Fix #![no_std] builds. #18
Merged
Conversation
This file contains 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
#![no_std] builds do not import alloc crate types such as String or Box into the default scope automatically, requiring them to be imported manually. This commit adds explicit use statements for those types to resolve build failures when building with the "std" feature disabled. Closes bodil#17.
|
I wonder if this PR will be merged soon? Right now I'm pulling from @okready 's branch instead of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #17.
This adds
usestatements to importalloctypes such asString,Box, andToStringmanually to resolve#![no_std]build issues.I also have a separate commit with an update to the GitHub Actions CI configuration to add
cargo checkand Clippy tests withstddisabled. If it's acceptable, I can combine it with this PR or create a separate PR with it once this is merged.