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 an awesome crate, but unfortunately fails to build on no_std projects.
This PR adds support for no_std builds by adding a std feature, which when is disabled enables no_std environments.
bytes-utils dependencyTo make this work, a similar change for bytes-utils was needed: vorner/bytes-utils#3.So I just pointed
Cargo.toml
to the PR forkFeel free to suggest another approach if you are not happy with that (e.g. pinning to hash, using dependency patch, just wait for the other PR, etc.).Code formatting
Seems
cargo fmt
was not executed for a while. So I skipped this step for not messing up this PR with code style changes.Circle CI
In my opinion, it makes sense to add a CI step to check for successful no_std builds.
Unfortunately, cargo always compiles dev dependencies, even for release builds. Cargo flag avoid-dev-deps is fixing this, but is still unstable. So the CI job is testing only nighly Rust for now.
Looking forward to your feedback!