Partial support for no_std #136
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the first step to support
no_std. I've flattened imports (to make the next step easier), replacedstdwithcoreandallocwherever is possible, and replacedwrite!with alloc-only equivalent in a few places. I also fixed some of the clippy warnings along the way in the parts of the code that I've touched.If that's something you're interested in having upstream, I'll bring in a follow-up PR the final support for
no_std, with a feature-flag propagating into dependencies.I do this work as an experiment to add Lua support into Firefly Zero handheld game console. We're compiling apps into non-wasi wasm environment (in case of Rust, wasm-unknown-unknown) but the mainstream Lua interpreter can be used only with Emscripten JS polyfill.