Byteyarn: Add no_std support
#13
Open
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.
Most of this PR is just changing
stdtocore/alloc.A couple off modules imported
std::allocwhich creates a problem when using anything fromliballoc, so I used::alloc::..in a number of places, IMO a bit smelly but the easiest and least invasive option.Usually
no_stdcompatible crates include a "std" default feature flag to enablelibstdbut nothing in byteyarn actually useslibstdso I didn't bother. This may create a breaking change in the future iflibstdis ever required so I can add a feature flag if you want.is in lib.rs, for "Macro stuff" which I've changed to
pub extern crate core as std;for fear of breaking things. From what I can see this is required by theyarn!macro. It may be better to remove this entirely and changeyarn!to use::core::fmt::format_args!instead.