-
Notifications
You must be signed in to change notification settings - Fork 202
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
Target stable Rust #242
Comments
Probably the hardest dependencies at this point are:
Incidentally, these are also the three features that tarpc users have to enable. |
|
Regarding |
That's true, but I'd rather only do that as a last resort (i.e. if usage of all other unstable features were removed and a user was asking for it immediately). It's hugely more maintainable to use async/await. And it's only one release away :) |
It was actually quite easy to get rid of |
async-await has hit beta, it's time to cross off the remaining feature flags asap. |
This is a full list of feature flags used by tarpc.
integer_atomicstry_traitarbitrary_self_typesasync_closureNow that Futures 1.0 have arrived I believe we can start dropping them one by one until tarpc works on stable Rust.
Continued from #131.
The text was updated successfully, but these errors were encountered: