Allow for no-std build (extracts std feature, on by default) #13
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.
The only things keeping rtp-rs from building on no-std are
RtpPacketBuilder::build
(build_into
is fine), the two Error trait impls, some references tostd
that could becore
, and some use offormat!
in error messages. After Rust 1.18 the errors can be no-std as well sincestd::error::Error
is moving tocore
. But in the meantime I've got this branch that makes this usable, so I figured I'd share it and see if you're interested in supporting that usecase.Tests, including doc tests, all still work, though I've moved them to use
build_into
except for a doc test that showsbuild
still does it's thing. They both delegate the real work tobuild_into_unchecked
so it seemed reasonable to me, but let me know if you feel differently.