(0.8.0)
parallel\Runtime::run — Execution
Shall schedule task for execution in parallel.
Shall schedule task for execution in parallel, passing argv at execution time.
Closures scheduled for parallel execution must not:
Instructions prohibited in Closures intended for parallel execution are:
Bilginize:
Nested closures may yield or use by-reference, but must not contain class or named function declarations.
Bilginize:
No instructions are prohibited in the files which the task may include.
Arguments must not:
Bilginize:
In the case of file stream resources, the resource will be cast to the file descriptor and passed as int where possible, this is unsupported on Windows.
Internal objects generally use a custom structure which cannot be copied by value safely, PHP currently lacks the mechanics to do this (without serialization) and so only objects that do not use a custom structure may be shared.
Some internal objects do not use a custom structure, for example parallel\Events\Event and so may be shared.
Closures are a special kind of internal object and support being copied by value, and so may be shared.
Channels are central to writing parallel code and support concurrent access and execution by necessity, and so may be shared.
A user class that extends an internal class may use a custom structure as defined by the internal class, in which case they cannot be copied by value safely, and so may not be shared.
The return parallel\Future must not be ignored when the task contains a return or throw statement.
Shall throw parallel\Runtime\Error\Closed if parallel\Runtime was closed.
Shall throw parallel\Runtime\Error\IllegalFunction if task is a closure created from an internal function.
Shall throw parallel\Runtime\Error\IllegalInstruction if task contains illegal instructions.
Shall throw parallel\Runtime\Error\IllegalParameter if task accepts or argv contains illegal variables.
Shall throw parallel\Runtime\Error\IllegalReturn if task returns illegally.