Is moving to futures and async/await being considered?

[dlight]

I note that crust depends on mio directly and doesn't use futures, which is a solid choice for a project that started many years ago (when futures in its present form didn't exist, and there were multiple competing async frameworks that were eventually abandoned).

Now that async/await is hitting stable (in 1.39), I was wondering if there were any plans to use it. Benefits would include better integration with other runtimes, leveraging executors with work-stealing threadpools like tokio, and easier to write state machines with async/await.

What do you think?