aboutsummaryrefslogtreecommitdiff
path: root/hash.go
Commit message (Collapse)AuthorAgeFilesLines
* hash: Make streaming hashes possibleGravatar Runxi Yu2026-01-291-0/+16
|
* hash: Use a hashAlgorithmDetails struct for single source of truth v0.1.2Gravatar Runxi Yu2026-01-271-42/+70
| | | | | | hashAlgorithm's are assumed to be valid; methods on invalid hashAlgorithms will panic from out-of-bounds read when it's not found in hashAlgorithmTable and that's expected and intended.
* hash: Document maxHashSize properlyGravatar Runxi Yu2026-01-191-19/+21
|
* hash: Key by algorithm, not sizeGravatar Runxi Yu2026-01-171-10/+51
|
* hash: data after sizeGravatar Runxi Yu2025-11-281-1/+1
| | | | | | This guarantees ... I guess ABI stability of where the size is, regardless of the version which may have different maxHashSize. Not too useful but I guess good practice
* Fix some docs and API typesGravatar Runxi Yu2025-11-161-1/+1
|
* Documentation overhaulGravatar Runxi Yu2025-11-161-3/+3
|
* Make the API more consistentGravatar Runxi Yu2025-11-161-6/+6
|
* hash: Make fewer helper functions need explicit hash length fieldsGravatar Runxi Yu2025-11-161-29/+24
|
* Revert "hash: Generic hash-algorithm API"Gravatar Runxi Yu2025-11-161-63/+35
| | | | | | | This reverts commit 94bfb1fa147f80e6ec39009d41fc2f853925e0a5. Generics actually kinda suck for these purposes... once you look at it from the user's perspective.
* hash: Generic hash-algorithm APIGravatar Runxi Yu2025-11-161-35/+63
|
* Support multiple hash sizes in one buildGravatar Runxi Yu2025-11-161-10/+33
|
* Use SHA-256 by defaultGravatar Runxi Yu2025-11-151-7/+0
|
* Initial commitGravatar Runxi Yu2025-11-131-0/+40