| 14 Oct 2025 |
 raitobezarius | The only value I see goes beyond hashes personally | 16:25:12 |
 K900 | convertHash is a massive hammer for a tiny nail | 16:25:19 |
| raitobezarius | I see people who wants to use base32 data inside non-hashes | 16:25:19 |
| raitobezarius | For valid reasons | 16:25:23 |
| raitobezarius | If it ends up constructing convertHash, fine | 16:25:33 |
| raitobezarius | But that's not my sole motive for spawning these primops | 16:25:49 |
 emily | so Nixpkgs would need
- parsing and serialization for SRI and
<algo>:<digest> that matches the implementation
- a lookup table between hashes and byte sizes
and the code would be Lix-specific (because Nix has chosen that strings cannot contain NUL bytes so the intermediate values would not be valid)
that may be fine
| 16:26:06 |
| raitobezarius | I'd say that the code is specific to those who have !(builtins?convertHash) true but idk | 16:26:48 |
| emily | if you're going to allow NUL bytes in strings you surely want to be able to handle Base64 etc. in general | 16:26:52 |
| raitobezarius | I mean you're right | 16:26:53 |
| raitobezarius | Perhaps, we should advertise NUL in our bytes lol | 16:27:01 |
| emily | Nix32 on the other hand is cursed | 16:27:02 |
| K900 | That's a much later problem tbh | 16:27:02 |
| raitobezarius | builtins.features.canContainNULInStrings | 16:27:06 |
| K900 | And definitely not a convertHash sized problem | 16:27:09 |
| emily | AIUI NUL bytes have already been decided to be allowed. | 16:27:22 |
