stream-cipher: remove NewBlockCipher bound on FromBlockCipher #333
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.
Note: breaking change.
As far as I can tell this was an oversight:
FromBlockCipher
never needs to instantiate a new block cipher (isn't that the point?), making this bound needlessly limiting.The rationale for it in the first place appears to be for the blanket impl of
NewStreamCipher
forC: FromBlockCipher
which needs it, but we can add the bound to the blanket impl, rather than (needlessly) sticking it on the trait.