-
Notifications
You must be signed in to change notification settings - Fork 14
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
no_std
support
#4
Comments
Hmm - I don't have any experience with
so it'll use whatever That being said, it is a bit of a usability fail to have to import
instead. What do you reckon? |
use so this crate can no longer depend on |
That unfortunately doesn't work on pub struct Wrapper<T>(core::pin::Pin<alloc::boxed::Box<dyn core::future::Future<Output = T> + Send>>); gives the error:
I think my opinion here has coalesced with the comments in dtolnay/async-trait#163. For #![no_std]
extern crate alloc;
use alloc::boxed::Box;
#[async_recursion::async_recursion]
async fn foo<T>(_t: T) {} |
Can this crate be made to use just
alloc
crate instead of beingstd
dependant? That would help a lot of embedded developers given that the most recent version of rust allows async await inno_std
scenarios out of the box.The text was updated successfully, but these errors were encountered: