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: Ic4aa9cc12a9874d4e7897c6f64408f10aa36fc82 |
||
---|---|---|
.. | ||
rl-next | ||
src | ||
theme | ||
anchors.jq | ||
book.toml | ||
custom.css | ||
generate-builtin-constants.nix | ||
generate-builtins.nix | ||
generate-manpage.nix | ||
generate-xp-features-shortlist.nix | ||
generate-xp-features.nix | ||
local.mk | ||
quote-literals.xsl | ||
redirects.js | ||
utils.nix |