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

Move to a no_std Implementation #122

Open
appcypher opened this issue Dec 13, 2022 · 2 comments
Open

Move to a no_std Implementation #122

appcypher opened this issue Dec 13, 2022 · 2 comments

Comments

@appcypher
Copy link
Member

Apart from intrinsic memory allocation needed for collections, smart pointers, etc., the library does not depend on a lot of system functions that the OS provides therefore making it a good candidate for a no_std implementation with just the alloc and collection features enabled.

There is really no pressing need for this now and requirements might change as the implementation evolves. But it would be nice to enforce this non-dependency somehow so this issue is here for that as well as other needs for it in the future.

@zeeshanlakhani
Copy link
Contributor

Thanks for writing this up @appcypher.

@matheus23
Copy link
Member

As of last week, async_once_cell (which we're using) has support for no_std.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants