RFC: no_std #63
Open
RFC: no_std #63
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
aep
force-pushed
the
no_std
branch
2 times, most recently
from
c10d34c
to
b1c4512
Compare
|
Great! Makes sense to do this change now. I'll check it out more once it passes CI. I'm down for re-adding HACL*, I removed it because we had an issue right before the 0.6 release and I wanted to be safe and re-integrate it after further inspection. |
|
Hello, Jake and Arvid I was wondering if you have plans to integrate this change and enable no_std support. I would love to use your library in our project that runs inside of the TEEs. Please let me know what you think. Cheers! |
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.
#62
the only thing that actually requires std is Cursor in src/resolvers/default.rs CipherChaChaPoly
and getrandom, which is an upstream issue in rand
both don't seem a big problem to me, since embedded users need a different resolver anyway now that hacl is gone