block-buffer v0.11 #823
Merged
block-buffer v0.11 #823
Conversation
This file contains hidden or 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
newpavlov
force-pushed
the
hex_literal_0.11
branch
from
87858fb to
aa2ccfc
Compare
newpavlov
added a commit
that referenced
this pull request
Nov 7, 2025
### Added - `ReadBuffer` type ([#823]) - Optional implementation of the `Zeroize` trait ([#963]) - Generic `serialize` and `deserialize` methods ([#1200]) - `ReadBuffer::{read_cached, write_block, reset}` methods ([#1201]) ### Changed - Block sizes must be bigger than 0 and smaller than 256. This is enforced using compile-time monomorphization errors. ([#1115]) - Size of `EagerBuffer` is equal to buffer size, while previously it was equal to buffer size plus one byte ([#823]) - Edition changed to 2024 and MSRV bumped to 1.85 ([#1149]) ### Removed - `EagerBuffer::set_data` method. Use the `ReadBuffer` type instead. ([#823]) [#823]: #823 [#963]: #963 [#1115]: #1115 [#1115]: #1116 [#1149]: #1149 [#1200]: #1200 [#1201]: #1201
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.
Depends on RustCrypto/traits#1172
The
BlockSizeschange is introduced to work around the leaky bounds problem.Added
ReadBuffertypeserializeanddeserializemethodsChanged
crypto_common::BlockSizestrait, which is implemented for types fromU1toU255EagerBufferis equal to buffer size, while previously it was equal to buffer size plus one byte.Removed
EagerBuffer::set_datamethod. Use theReadBuffertype instead.