Feb. 16, 2020
10:52 p.m.
On Sun, 16 Feb 2020 17:41:36 -0500 Kyle Stanley <aeros167@gmail.com> wrote:
As a side note, are we still interested in expanding the public API for the Future class? Particularly for a public means of accessing the state. The primary motivation for it was this topic, but I could easily the same issues coming up with custom Future and Executor classes; not to mention the general debugging usefulness for being able to log the current state of the future (without relying on private members).
That sounds useful to me indeed. I assume you mean something like a state() method? We already have Queue.qsize() which works a bit like this (unlocked and advisory). Regards Antoine.