Read the first sentence. > This blog post describes a proposed scheduler for async-std that did not end up being merged for several reasons. I don't think it'

Read the first sentence. > This blog post describes a proposed scheduler for async-std that did not end up being merged for several reasons. I don't think it's a particularly good idea in the first place - it's basically an automatic watchdog-driven block_in_place(). It doesn't remove the problem of blocking in futures, it just limits the damage to the local task rather than blocking the entire executor. That's fine in the simple case of future-per-task, but it's pretty common to be polling multiple futures concurrently within one, so it's not a general solution.