You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, it looks like this will always execute using async_std::task::block_on. I bet that will work great for most scenarios, and if that's intended to be the full scope of this crate, that makes sense! 😊
My feature idea is: for use cases that demand extremely small code size, fast compile time, deployment on an exotic platform, the ability to use multiple threads, or maybe just to support someone's preference for a certain executor, what do you think of making the executor pluggable? To be up front, I'm interested in using this with spin_on because I have some non-performance intensive code and I'm looking for really fast compile times.
I can think of two variations of this:
Explicitly support several useful executors
Allow the user to specify their own executor function with a signature similar to fn block_on<F, T>(future: F) -> T where F: Future<Output = T>
I'm pretty sure that this is feasible and I'd be happy to fill in some technical details if this sounds like a desirable feature.
The text was updated successfully, but these errors were encountered:
Right now, it looks like this will always execute using
async_std::task::block_on
. I bet that will work great for most scenarios, and if that's intended to be the full scope of this crate, that makes sense! 😊My feature idea is: for use cases that demand extremely small code size, fast compile time, deployment on an exotic platform, the ability to use multiple threads, or maybe just to support someone's preference for a certain executor, what do you think of making the executor pluggable? To be up front, I'm interested in using this with
spin_on
because I have some non-performance intensive code and I'm looking for really fast compile times.I can think of two variations of this:
fn block_on<F, T>(future: F) -> T where F: Future<Output = T>
I'm pretty sure that this is feasible and I'd be happy to fill in some technical details if this sounds like a desirable feature.
The text was updated successfully, but these errors were encountered: