no_std support with alloc
#183
Open
+267
−64
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
Added basic no_std support by switching to `core` and `alloc` libraries wherever possible. Restructured features in Cargo.toml to allow for customized setups with or without the standard library.
|
FYI @mcginty |
|
Ping @mcginty, any thoughts or comments on this? Would love to get these changes upstreamed eventually :) |
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.
Basic
no_stdsupport for environments whereallocis provided.default-resolverwith or withoutstdBasically all crypto primitives are now individually selectable with
use-xxx-yyyfeatures. Users can build their own combinations of DH + Crypto + Hash withdefault-resolverto create minimal builds without the standard library for embedded targets.lib.rsincludes a safeguard to make sure that all required components are provided at build time.This changes the feature flag interface of this crate a bit, but existing features are left in place for the sake of backwards compatibility.
Providing
no_stdsupport for other resolvers beside the default one is not in the scope of this PR.#62
#179