no_std support (with default-enabled "std" cargo feature) #255
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
tarcieri
force-pushed
the
no_std
branch
2 times, most recently
from
621104f to
a10eb40
Compare
Feature gates anything dependent on `std` on the eponymous cargo feature, and changes references to libcore features from `std` to `core`
|
Note: I'd also be happy to pursue this on the 0.5.x branch only, as I think there are some opportunities there to address other tough problems like the pervasive use of |
This was referenced Aug 14, 2019
|
Obsoleted by #281 |
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.
This PR revives #135 now that the
alloccrate is stable, which unlocks usingbytesin embedded RTOS environments or other embedded environments with enough RAM to warrant a heap (e.g. on SAMD51 uCs that have 192kB RAM).Like the original #135 actual
allocsupport will be added in a subsequent PR, and this is a first pass to add initialno_stdsupport and sanity check the approach.In absence of upstream support for this, I've had to create forks of bytes and forks of downstream consumers of bytes, so it'd be really swell to get this all upstream rather than forking!