lix/tests/functional/lang/eval-fail-dupAttr-inherit.err.exp

error: attribute 'a' already defined at /pwd/lang/eval-fail-dupAttr-inherit.nix:1:16
       at /pwd/lang/eval-fail-dupAttr-inherit.nix:1:19:
            1| { inherit ({}) a; a.b = 1; }
             |                   ^
            2|
report inherit attr errors at the duplicate name previously we reported the error at the beginning of the binding block (for plain inherits) or the beginning of the attr list (for inherit-from), effectively hiding where exactly the error happened. this also carries over to runtime positions of attributes in sets as reported by unsafeGetAttrPos. we're not worried about this changing observable eval behavior because it is marked unsafe, and the new behavior is much more useful. (cherry picked from commit 1edd6fada53553b89847ac3981ac28025857ca02) Change-Id: I2f50eb9f3dc3977db4eb3e3da96f1cb37ccd5174 2024-01-29 05:19:23 +00:00			`error: attribute 'a' already defined at /pwd/lang/eval-fail-dupAttr-inherit.nix:1:16`
diagnose duplicated attrs at correct path diagnose attr duplication at the path the duplication was detected, not at the path the current attribute wanted to place. doing the latter is only correct if a leaf attribute was duplicated, not if an attrpath was set to a non-attrset in one binding and a (potentially implied) attrset in another binding. fixes #124 Change-Id: Ic4aa9cc12a9874d4e7897c6f64408f10aa36fc82 2024-03-16 20:29:52 +00:00			`at /pwd/lang/eval-fail-dupAttr-inherit.nix:1:19:`
			`1\| { inherit ({}) a; a.b = 1; }`
			`\| ^`
			`2\|`