tvl-depot/tvix/eval/docs/language-issues.md
sterni 77b0dddc3d chore(tvix/eval): fix markdown labeled link syntax
Change-Id: I639dc0801090eaba56b61858e28204b5a0e631b6
Reviewed-on: https://cl.tvl.fyi/c/depot/+/8784
Reviewed-by: tazjin <tazjin@tvl.su>
Tested-by: BuildkiteCI
Autosubmit: sterni <sternenseemann@systemli.org>
2023-06-15 19:40:08 +00:00

2.3 KiB

Nix language issues

In the absence of a language standard, what Nix (the language) is, is prescribed by the behavior of the C++ Nix implementation. Still, there are reasons not to accept some behavior:

  • Tvix aims for nixpkgs compatibility only. This means we can ignore behavior in edge cases nixpkgs doesn't trigger as well as obscure features it doesn't use (e.g. __overrides).
  • Some behavior of the Nix evaluator seems to be unintentional or an implementation detail leaking out into language behavior.

Especially in the latter case, it makes sense to raise the respective issue and maybe to get rid of the behavior in all implementations for good. Below is an (incomplete) list of such issues:

On the other hand, there is behavior that seems to violate one's expectation about the language at first, but has good enough reasons from an implementor's perspective to keep them:

  • Dynamic keys are forbidden in let and inherit. This makes sure that we only need to do runtime identifier lookups for with. More dynamic (i.e. runtime) lookups would make the scoping system even more complicated as well as hurt performance.
  • Dynamic attributes of rec sets are not added to its scope. This makes sense for the same reason.
  • Dynamic and nested attributes in attribute sets don't get merged. This is a tricky one, but avoids doing runtime (recursive) merges of attribute sets. Instead all necessary merging can be inferred statically, i.e. the C++ Nix implementation already merges at parse time, making nested attribute keys syntactic sugar effectively.

Other behavior is just odd, surprising or underdocumented:

  • builtins.foldl' doesn't force the initial accumulator (but all other intermediate accumulator values), differing from e.g. Haskell, see the relevant PR discussion.