43c851bc84
The outer fingerprint used for store path calculation is always a sha256 digest. This includes both input and output-addressed store paths. We used a NixHash here, which can also represent other hash types, and that had a bunch of annoyances: - Whenever we had the bytes, we had to wrap them in a NixHash::Sha256(). - Things like AtermWriteable had to be implemented on NixHash, even though we then had an assertion it was only called in the NixHash::Sha256 case. Change-Id: Ic895503d9b071800d2e52ae057666f44bd0ab9d6 Reviewed-on: https://cl.tvl.fyi/c/depot/+/11142 Tested-by: BuildkiteCI Autosubmit: flokli <flokli@flokli.de> Reviewed-by: John Ericson <git@johnericson.me> Reviewed-by: picnoir picnoir <picnoir@alternativebit.fr> |
||
|---|---|---|
| .. | ||
| builtins | ||
| tests | ||
| .skip-subtree | ||
| decompression.rs | ||
| fetchurl.nix | ||
| known_paths.rs | ||
| lib.rs | ||
| refscan.rs | ||
| tvix_build.rs | ||
| tvix_io.rs | ||
| tvix_store_io.rs | ||