| 14 Oct 2025 |
 emily | I mean that if { algo, format, digest } is considered a "first-class" thing the implementation is consuming then it doesn't seem so weird to have a built-in that converts it at that point | 17:45:26 |
| emily | (the other potential use-cases like producing Nix32 filenames and converting lock file formats would remain regardless) | 17:45:44 |
 Qyriad | Filenames and lockfiles are a point in favor, but if the implementation consumes { algo, format, digest } in any form then you specifically wouldn't need to convert between them, no? | 17:46:54 |
| emily | I am not saying that you would need to convert them to pass them to a FOD fetcher. I'm saying that if the objection to a convertHash is "this is doing too much because these structured hashes aren't really a first-class implementation concept", but then you add support for structured hashes to FODs, then they are a first-class implementation concept and it doesn't seem too weird to have a conversion built-in for them. | 17:50:30 |
| emily | (and then that conversion built-in would be useful for the other use caess) | 17:50:41 |
| Qyriad | Ahh | 18:00:08 |
| * Qyriad nods | 18:00:10 |
