let bindings cause attrset key conflicts where merging is possible #651
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#651
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
In theory, these two snippets should evaluate to the same thing:
and
However, while the first one evaluates with no problem, the second form fails with the following error:
Steps To Reproduce
nix repl
)key.two = 2;
lineExpected behavior
Both attribute sets should evaluate to:
nix --version
outputwe understand why you expect this, but merging is syntactic sugar and your example cannot be syntactically rearranged into a merged definition. this is not a bug, it's behaving as intended (even though the the intended behavior is stupid)
Yeah, makes sense - totally understand closing this one as a wontfix, just figured I'd raise it as a point to maybe at least document somewhere, since it is a little unexpected.
oh we're not closing it! this is definitely something that needs to be worked on in some way, through documentation first and overhauling the merging semantics in the future :) though we should probably also add the docs labels to make this easier to find, huh