<title>refactor(tvix/eval): Don't (ab)use PartialEq for Nix equality</title>
<updated>2022-09-18T22:03:41+00:00</updated>
<author>
<name>Griffin Smith</name>
<email>root@gws.fyi</email>
...</author>
<published>2022-09-18T18:04:40+00:00</published>
<link rel="alternate" type="text/html" href="http://code.tvl.fyi/commit/?id=915ff5ac2a180cbd736ce8404c46566a14d484ba"/>
<id>urn:sha1:915ff5ac2a180cbd736ce8404c46566a14d484ba</id>
<content type="text">
Using rust's PartialEq trait to implement Nix equality semantics is
reasonably fraught with peril, both because the actual laws are
different than what nix expects, and (more importantly) because certain
things actually require extra context to compare for equality (for
example, thunks need to be forced). This converts the manual PartialEq
impl for Value (and all its descendants) to a *derived* PartialEq
impl (which requires a lot of extra PartialEq derives on miscellanious
other types within the codebase), and converts the previous
nix-semantics equality comparison into a new `nix_eq` method. This
returns an EvalResult, even though it can't currently return an error,
to allow it to fail when eg forcing thunks (which it will do soon).
Since the PartialEq impls for Value and NixAttrs are now quite boring,
this converts the generated proptests for those into handwritten ones
that cover `nix_eq` instead
Change-Id: If3da7171f88c22eda5b7a60030d8b00c3b76f672
Reviewed-on: https://cl.tvl.fyi/c/depot/+/6650
Autosubmit: grfn <grfn@gws.fyi>
Tested-by: BuildkiteCI
Reviewed-by: tazjin <tazjin@tvl.su>
</content>