You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ cue version
cue version v0.10.0
go version go1.23.0
-buildmode exe
-compiler gc
-trimpath true
CGO_ENABLED 0
GOARCH amd64
GOOS linux
GOAMD64 v1
cue.lang.version v0.10.0
Does this issue reproduce with the latest stable release?
At the very least, you can say the evalv3 behaviour is very inconsistent: If you change the _a+_b to either just _a or _b then the default i: *0 isn't applied. By changing the embedding to the _a+_b version, the default now is applied. This seems very unlikely to be the desired behaviour.
Additionally, I don't see why the default would be applied in this case at all -- by rule U1 of https://cuelang.org/docs/reference/spec/#default-values the default 0 should be being unified with the non-default 11 and that should turn into ⊥, thus ensuring the default never features subsequently.
What version of CUE are you using (
cue version
)?Does this issue reproduce with the latest stable release?
0.10.0 is latest.
What did you do?
What did you expect to see?
A passing test.
What did you see instead?
The text was updated successfully, but these errors were encountered: