RustCrypto / RustCrypto/hashes
`const fn` hashing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 340
- Avg merge
- 12h 31m
- Merged PRs (30d)
- 2
Description
Hi!
I'm using Shake256 in a setting where all input data is known at compile-time, a case where the hash value could be computed at compile-time too.
I've been using tiny-keccak before (I'm not sure why anymore, exactly), and I started toying with it to support const fn hashing. I've bounced on some hurdles, which is why I made that issue.
This week I realized I could probably start the same discussion here: how painful would const fn-hashing be to implement? I feel like it would probably not work due to the Digest family of traits (trait fns cannot be const afaik), but I'd nevertheless would want to discuss!
Best regards,
Ruben
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Digest family of traits and Rust's const fn restrictions, which the issue identifies as the main obstacle. No implementation files, tests, or concrete acceptance criteria are named; the work would first need an agreed approach and a definition of what compile-time Shake256 hashing should support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100