-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
const fn
hashing
#288
Comments
It will depend on progress of As a stopgap solution I would use build scripts to compute hashes over data. Maybe procedural macros could work as well? |
Thanks for documenting what needs to be in place!
I already have a build script in place, so it might make sense to do it in a build script indeed. It's generated code. It would be a bit cleaner without it though. What do you say, leave this issue open for now? I might get my hands dirty and make a |
There are already a few |
I was tempted to use |
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 supportconst 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 theDigest
family of traits (traitfn
s cannot beconst
afaik), but I'd nevertheless would want to discuss!Best regards,
Ruben
The text was updated successfully, but these errors were encountered: