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

investigate providing core library functionality in a no_std environment #20

Open
sdemos opened this issue May 1, 2018 · 0 comments
Open
Milestone

Comments

@sdemos
Copy link
Contributor

sdemos commented May 1, 2018

If enough of the heap allocation is removed from the core data structures and functions of this library, it should be possible to provide a no_std feature flag, so libraries and executables that are operating in a no_std environment can still use this library. It will likely remove some more complicated convenience functionality.

It's possible that this isn't a library that anyone will want to use in a no_std environment, but I think that if the work in #17 #18 #19 is complete, it should be relatively easy to allow this, so we might as well investigate it.

@sdemos sdemos added this to the v1.0.0 milestone May 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant