@pitr-ch the state of affairs for Future, Promises::Future & Promise is so confusing in the codebase.
I can't imagine anyone making sense of it unless they take the time to thoroughly read the docs.
I saw some issues tackling a "2.0" release -- I would definitely recommend deleting the outdated Future & Promise classes.
If major upgrade I would remove the
Promises:: module scoping as well.
Does someone have a good recommendation for how to accomplish this:
I'd like a ThreadPoolExecutor with a queue length of 0 which does not mean unbound.
Looks like it should be able to swap the queue for SynchronousQueue according to: