Scheduler Reference
Scheme for automatically assigning tasks to threads
What it is #
Position in the hierarchy #
| Inherits from | — |
| Does | — |
| Consumed by | CurrentThreadScheduler, ThreadPoolScheduler |
Routines #
Signatures are reproduced from the documentation, including their declared return types. A routine listed here is part of the type's published interface; whether Raku++ implements it is a separate question, answered by the examples below.
method uncaught_handler #
method uncaught_handler() is rw
RW-Accessor for the handler that is caught for uncaught exceptions from the code that is being scheduled and run.
method cue #
method cue(&code, Instant :$at, :$in, :$every, :$times = 1; :&catch --> Cancellation)
Returns Cancellation.
Schedules a callable (&code) for execution and returns an instantiated Cancellation object to cancel the scheduling of the code for execution (which is especially important if you specify the :every ( time ) named parameter). The adverbs control when and how the code is run: run. Alternatively $in is the number of seconds (possibly fractional) to wait before running the code. If $at is in the past or $in is negative,
method loads #
method loads()
This is a method stub, should be re-implemented when subclassing.
Examples, run three ways #
Every example below comes from the official documentation, together with the output that documentation asserts. Each was then executed by Rakudo and by Raku++ when this page was built. Where the three agree, one result is shown; where they do not, all three are — because which of them is wrong is exactly the information worth having.
1 no-output
role Scheduler {
has &.uncaught_handler is rw
}Not executed: the documentation states no expected output for this example.