The handler for the fatal errors that are not sent to
the failures stream of the isolate.
The handler for the fatal errors that are not sent to
the failures stream of the isolate.
Note:
If the failures reactive throws
while handling any throwables passed to it,
then those throwables are passed to this error handler.
This means that the handler can also receive non-fatal errors.
scala.util.control.NonFatal
Initiates the isolate frame.
Initiates the isolate frame. Clients never call this method directly.
The scheduler can use the schedulerInfo field of the isolate frame
to store its custom configuration objects for this isolate frame.
For example, a Scheduler based on a Java Executor would typically
store a Runnable object here and later use it from the schedule method.
the type of the isolate event queue
the isolate frame to initiate
Schedules an isolate frame for execution.
Schedules an isolate frame for execution. Clients never call this method directly.
This method uses the isolate frame to flush messages from its event queue and propagate events through the isolate.
the type of the isolate event queue
the isolate frame to schedule
(scheduler: StringAdd).self
(scheduler: StringFormat).self
(scheduler: ArrowAssoc[Scheduler]).x
(Since version 2.10.0) Use leftOfArrow instead
(scheduler: Ensuring[Scheduler]).x
(Since version 2.10.0) Use resultOfEnsuring instead
An object that schedules isolates for execution.
After an isolate is instantiated, its isolate frame is assigned a scheduler by the isolate system. An isolate that is assigned a specific scheduler will always be executed on that same scheduler.
After creating an isolate, every isolate system will first call the
initiatemethod on the isolate frame. Then, the isolate system will call theschedulemethod every time there are events ready for the isolate.Note: Clients never invoke
Scheduleroperations directly, but can implement their own scheduler if necessary.org.reactress.IsolateSystem