eldritch horrors
11f35afa6f
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:
|
||
---|---|---|
.. | ||
functional | ||
installer | ||
nixos | ||
unit |