Tracking Issue for Hasher::{write_str, write_length_prefix}
(feature(hasher_prefixfree_extras)
)
#96762
Labels
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
Feature gate:
#![feature(hasher_prefixfree_extras)]
This is a tracking issue for the new provided methods on
Hasher
added to fix #94026write_str
lets the hasher customize how it works withstr
, so it can use theb'\xFF'
trick if it's byte-wise, or a different approach if it does chunked rounds.write_length_prefix
gives an obvious choice when implementingHash
for collections (likeVecDeque
) which can't just use the slice hash, and allows the hasher to optimize how best to represent the length.Public API
Steps / History
Hasher
#94598Unresolved Questions
write_str
provided implementation be? It was added matching the previousimpl Hash for str
behaviour to get in without breaking hash checks (like the one incargo
), but that's not always prefix-free (it depends on the round strategy), so there's an argument that a different implementation would be better.The text was updated successfully, but these errors were encountered: