feat(aes-gcm-siv): re-export aes crate
#603
Merged
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 to ensure consistency with it's sister `aes-gcm` crate, which also re-exports `aes` (aes-gcm/src/lib.rs:114). finds specific use in defining a `Key` generic for example; it takes a `KeySizeUser` which are a majority `Aes*` structs from `aes`.
|
Thanks |
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.
added to ensure consistency with it's sister
aes-gcmcrate, which also re-exportsaes(aes-gcm/src/lib.rs:114).finds specific use in defining a
Keygeneric for example; it takes aKeySizeUserwhich are a majorityAes*structs fromaes, such as:Key<Aes256>.this change allows the consumer to just reference the re-export as opposed to pulling in the entire
aescrate to their own crate. i was pivoting fromaes-gcmtoaes-gcm-sivmyself when i came across this and took it upon myself to smooth out the discrepancy.