Description
openedon May 5, 2020
@tkf and me have been discussing ways to propagate information about available workers (or resources in general) in distributed hierarchical computations:
Adding resource arguments to every function call would be impractical, and using Cassette & friends to add add context by rewriting the whole computation would be very heavy-handed, since it might tough large code stacks (and may also be not be a complete solution when remote calls are involved?).
Could we add something like a context
field to Task
, in addition to the storage
field - with the difference that context
is automatically propagated to spawned tasks and remote calls? Adding the possibility to propagate a context through a computation in this fashion could also be useful for other use cases too, I think.