ThreadPool
instances, it should be possible
thread_shutdown
or something... Not the prettiest thouh
exit_handler
, I mean :)
spawn_future
is probably the most interesting thing we have to discuss :)
async
is still a bit magic to me
I guess if the async work leading up to our part isn't ready, we'd just return NotReady too and let some outer executor deal with it?
spawn_future(F: impl Future)
, we would schedule a job that calls F::poll
, indeedWaker
that is tied to rayon, I thinkNotReady
(due to some I/O event), and it would have clone'd our Waker
to hold on to itwake
method; this would cause us to add the job back to the (Rayon) thread-pool, at which point we go back to step 1