Add finish_into
to write the hash to a user provided buffer.
#22
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.
This avoids needing to allocate a vector for every hash on Windows and
Linux. The CommonCrypto API will work but still allocates a vector.
The buffer must match the digest size exactly or panic. An undersized
buffer would violate Rust safety guarantees, but an oversized buffer
could also be problematic if, e.g., the user passed a 32 byte buffer
into a 20 byte digest without zeroing it first.
The main benefit is performance when hashing enormous numbers of
values, but this can also be more ergonomic in certain cases.
Consider:
lib.rs
which should callflush
after writing to the Hasher.