4 ms·
> But, and it’s not stable yet, futures and executors, the two traits, are being added to the standard library. Is this implementation going to wrap epoll/kque
by MuffinFlavored 8y ago
> But, and it’s not stable yet, futures and executors, the two traits, are being added to the standard library.
Is this implementation going to wrap epoll/kqueue/iocp?
Would you say Tokio has any drawbacks/flaws/design choices yo aren't a fan of?
What are the popular choices other than Tokio?
- steveklabnik 8y agoTraits are not implementations, just interfaces. There won't be an implementation of one in std, just the interface, so that the ecosystem can interoperate. At the moment, I think Tokio is pretty great. I wish that there was more development bandwidth to help test out some cutting-edge stuff, but I think the design is sound. It really depends, Tokio is the most popular at the moment. This is because most of the new ecosystem is built around these new, unstable interfaces. Tokio currently runs on the older, not in the standard library one. It's all a bit confusing at the moment, to be honest.