… | |
… | |
210 | Similar to C<async>, but uses a coroutine pool, so you should not call |
210 | Similar to C<async>, but uses a coroutine pool, so you should not call |
211 | terminate or join (although you are allowed to), and you get a coroutine |
211 | terminate or join (although you are allowed to), and you get a coroutine |
212 | that might have executed other code already (which can be good or bad :). |
212 | that might have executed other code already (which can be good or bad :). |
213 | |
213 | |
214 | Also, the block is executed in an C<eval> context and a warning will be |
214 | Also, the block is executed in an C<eval> context and a warning will be |
215 | issued in case of an exception instead of terminating the program, as C<async> does. |
215 | issued in case of an exception instead of terminating the program, as |
|
|
216 | C<async> does. As the coroutine is being reused, stuff like C<on_destroy> |
|
|
217 | will not work in the expected way, unless you call terminate or cancel, |
|
|
218 | which somehow defeats the purpose of pooling. |
216 | |
219 | |
217 | The priority will be reset to C<0> after each job, otherwise the coroutine |
220 | The priority will be reset to C<0> after each job, otherwise the coroutine |
218 | will be re-used "as-is". |
221 | will be re-used "as-is". |
219 | |
222 | |
220 | The pool size is limited to 8 idle coroutines (this can be adjusted by |
223 | The pool size is limited to 8 idle coroutines (this can be adjusted by |