Skip to main content
Drupal API
User account menu
  • Log in

Breadcrumb

  1. Drupal Core 11.1.x
  2. Driver.php

function Driver::__debugInfo

Returns some useful information about the event loop.

If this method isn't implemented, dumping the event loop in a busy application, even indirectly, is a pain.

Return value

array

2 methods override Driver::__debugInfo()
AbstractDriver::__debugInfo in vendor/revolt/event-loop/src/EventLoop/Internal/AbstractDriver.php
Returns some useful information about the event loop.
TracingDriver::__debugInfo in vendor/revolt/event-loop/src/EventLoop/Driver/TracingDriver.php
Returns some useful information about the event loop.

File

vendor/revolt/event-loop/src/EventLoop/Driver.php, line 317

Class

Driver
The driver MUST run in its own fiber and execute callbacks in a separate fiber. If fibers are reused, the driver needs to call {

Namespace

Revolt\EventLoop

Code

public function __debugInfo() : array;

API Navigation

  • Drupal Core 11.1.x
  • Topics
  • Classes
  • Functions
  • Constants
  • Globals
  • Files
  • Namespaces
  • Deprecated
  • Services
RSS feed
Powered by Drupal