-
Notifications
You must be signed in to change notification settings - Fork 341
Add future::poll_fn #123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add future::poll_fn #123
Conversation
@kpp It's because we want to provide stronger stability guarantees, a more faithful feel of We're still compatible with traits |
Committing to stability of unstable features may be not the right idea. I understand that std should feel stable, but it's as stable as its constituent parts - and async-std has at least half of it pretty unstable still. |
I'm not sure why folks are downvoting the clarification from @stjepang, We're committed to providing an ergonomic async counterpart to stdlib that's fully compatible with the core traits and async ecosystem underpinned by So I'd like to take a moment here to provide some clarity: we're happy to answer any questions about design in earnest, but we're not going to change the design direction of this crate. If this is something you disagree with, that's okay -- but it might be good to realize this crate is not for you. I hope this makes sense; I prefer being clear on these kinds of matters for the benefit of everyone involved. @stjepang lol I just wrote #124 with the exact same API. Seems like we had the same idea at the same time! |
Closing in favor of #124 |
No description provided.