9b4dda6222
- Update pkg-descr - Take maintainership Changes: https://metacpan.org/changes/distribution/Coro
18 lines
1,015 B
Text
18 lines
1,015 B
Text
Coro started as a simple module that implemented a specific form of first class
|
|
continuations called Coroutines. These basically allow you to capture the
|
|
current point execution and jump to another point, while allowing you to return
|
|
at any time, as kind of non-local jump, not unlike C's setjmp/longjmp. This is
|
|
nowadays known as a Coro::State.
|
|
|
|
One natural application for these is to include a scheduler, resulting in
|
|
cooperative threads, which is the main use case for Coro today. Still, much of
|
|
the documentation and custom refers to these threads as "coroutines" or often
|
|
just "coros".
|
|
|
|
A thread is very much like a stripped-down perl interpreter, or a process:
|
|
Unlike a full interpreter process, a thread doesn't have its own variable or
|
|
code namespaces - everything is shared. That means that when one thread modifies
|
|
a variable (or any value, e.g. through a reference), then other threads
|
|
immediately see this change when they look at the same variable or location.
|
|
|
|
WWW: https://metacpan.org/release/Coro
|