-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
cue: fix Value.Unify closedness issues for evalv3
When using Unify to unify cue.Values, the conjuncts of each value need to be grouped into their own closeContext. This prevents conjuncts that are interpreted as embeddings (e.g. because they are wrapped in a StructLit associated with a file) from erasing closedness. Basically, when unifying {close({})} and {a: 5}, the former should not be treated as an embedding that is at the same level as the latter. The fix generally improves closedness check behavior for V3, and thus we could also disable the use of "allowed" for V3. This is good, as this function does not work well for V3. This means that all test cases of Issue 3562 could be fixed. This fix also fixes discrepancies in TestAPI, which were resulting from not replicating the V2 logic in V3. We include this change in the same CL as it uses the same mechanism and it will be useful to consider these together when studying this change down the line. Fixes #3562 Signed-off-by: Marcel van Lohuizen <[email protected]> Change-Id: If6acd2a1ec7f10928180688782d1fae4a3a8ca00 Dispatch-Trailer: {"type":"trybot","CL":1204365,"patchset":3,"ref":"refs/changes/65/1204365/3","targetBranch":"master"}
- Loading branch information
Showing
15 changed files
with
99 additions
and
118 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.