evalv3: field not allowed

[uhthomas]

What version of CUE are you using (cue version)?

$ go run cuelang.org/go/cmd/[email protected] version
cue version v0.10.0-alpha.2.0.20240726102249-5de5b42c834f

go version go1.22.5
      -buildmode exe
       -compiler gc
     CGO_ENABLED 1
          GOARCH amd64
            GOOS linux
         GOAMD64 v1
cue.lang.version v0.10.0

Does this issue reproduce with the latest stable release?

What did you do?

import "list"

#A: {
	let b = {}

	c: b & {
		d: 1
	}
}

list.Concat([[#A]])

What did you expect to see?

$ go run cuelang.org/go/cmd/[email protected] export ./a.cue
[
    {
        "c": {
            "d": 1
        }
    }
]

What did you see instead?

$ CUE_EXPERIMENT=evalv3 go run cuelang.org/go/cmd/[email protected]
0.0.c.d: field not allowed:
    ./a.cue:6:5
    ./a.cue:7:3
exit status 1

[uhthomas]

Really bizarre. This fails:

import "list"

#A: {
	let b = {}

	c: #B & b & {
		d: 1
	}
}

#B: d: int

list.Concat([[#A]])

This doesn't:

import "list"

#A: {
	c: #B & {
		d: 1
	}
}

#B: d: int

list.Concat([[#A]])

This is also okay:

import "list"

#A: {
	c: #B & {} & {
		d: 1
	}
}

#B: d: int

list.Concat([[#A]])

[uhthomas]

this is okay though.

import "list"

#A: {
	let b = #B & {}

	c: b & {
		d: 1
	}
}

#B: d: int

list.Concat([[#A]])

[mpvl]

Analysis: Similar to #3330. Normally referencing a struct within a definition does not affect closeness. In other words, this is allowed according to the spec:

#A: {
   b: c: int
   d: b
   d: e: int
}

Referencing in #A seems to trigger a different behavior in some cases, so that a reference like b treats it as closed.