pmap feature request to facilitate dynamic scheduling

code that is called by pmap() should have the ability to signal to the scheduler a (dynamic) determination not to schedule any more new tasks. existing tasks should either be finished or aborted, depending on signal.

For example, after any one task function has signaled “TASKSNONEW”, the scheduler should stop scheduling further processes, but let’s the remaining tasks finish (e.g., we already found the alien, when the search parties come back, don’t send them out again); when any one task function signals “TASKSALLABORT”, the scheduler should further immediately terminates all other tasks ( (e.g., the alien has found us, is hostile, and we will need all search parties to come back immediately to help defend the base).

I think this is in the spirit of pmap, but greatly improves its previously static functionality to become dynamic. I also hope that it can be implemented with relatively little pain to the developers (catch interrupt?) and to the user. it becomes much easier for the user to signal “done” than having to write their own schedulers---a more obscure task.

In addition, I think the pmap() call should have arguments to set timeouts, both for itself and for individual tasks.

Start by reading the pmap implementation and its scheduler entry points; the issue does not identify specific files or tests. Define how TASKSNONEW, TASKSALLABORT, and self/task timeouts should be represented and coordinated, then verify the behavior with coverage for stopping scheduling, aborting tasks, and timeout handling.