-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
Feature-gate async_trait
in lieu of new, standardized async_fn_in_trait
feature.
#236
Comments
for now |
Sadly this doesn't work yet as native async trait futures aren't |
That isn't completely true, if you specify the desurgared form in a trait definition you can specify additional bounds (like You can see this in action here: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=ec570d1da8499bb14e80bac0827e233b Comment out the |
Thanks for the tip! I gave it a try and unfortunately I'm running into rust-lang/rust#110338 If you want to give it a try: #244 |
As a complete alternative (a large, hairy alternative), it might be a good evolution to implement proper |
Would it be possible to put the
async-trait
stuff behind a feature of the same name, and then use a#[cfg_attr(feature = "async-trait", ::async_trait::async_trait)]
for all occurrences, such that we can use the newly stabilizedasync
-in-trait functionality?The text was updated successfully, but these errors were encountered: