Skip to content
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? #103

Closed
huangjj27 opened this issue May 10, 2020 · 4 comments
Closed

no_std support? #103

huangjj27 opened this issue May 10, 2020 · 4 comments

Comments

@huangjj27
Copy link

Recently I read that zCore has implemented async/await support on OS level by making their own executor, proving that async runtime can be run on no_std. Can we also support no_std?

@alilleybrinker
Copy link

I believe no_std support for async/await is coming with the next Rust version.

@ghost
Copy link

ghost commented May 10, 2020

Well, which parts of smol would even be available in no_std environments? :) The reactor requires networking, which is provided by std. Blocking executor doesn't make sense without types for stdin/stdout/stderr and files. I could be missing something here, though!

@llebout
Copy link
Contributor

llebout commented May 14, 2020

I'm guessing this goes hand in hand with providing an interface for people to implement their own reactors. Embedded typically has to come up with their own TCP/IP stack like LWIP or PicoTCP.

See for example, this project that implements support for them: https://github.com/cesanta/mongoose

@ghost
Copy link

ghost commented Aug 28, 2020

Closing this issue due to inactivity. I don't think it makes too much sense for smol to provide anything no_std. That would basically entail some parts of futures-lite, which you can use directly and disable the std feature flag in it.

@ghost ghost closed this as completed Aug 28, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants