Daniel Martí
Daniel Martí
Note that this spec deviation bug will disappear with the `aliasv2` language change: https://github.com/cue-lang/cue/discussions/4014
Still happens as of v0.15.0.
Reduced to the following testscript: ``` exec cue export in.cue -- in.cue -- #Object: version!: "v1" #Output: (#Object.version): #Object out: #Output out: v1: version: "v1" ``` Below are the results...
In other words, the commit that we bisected is a bugfix; older versions of CUE did not correctly apply the required field semantics outlined in the language spec.
With @cuematthew we're in agreement that this should indeed fail, and that commit was a bugfix, but that the error you're seeing now is not ideal. I'll repurpose this issue...
What was the purpose of this issue? It contains no context and hasn't been updated at all since October 2022. cc @4ad
My understanding is that there are no plans to continue this work anytime soon, so I suggest that we close this issue for now to reflect that. We can always...
OK, Marcel shows that this panic also exists with old aliases: ``` exec cue export in.cue -- in.cue -- z=#Def: { _, _out: { if (z & string) != _|_...
Lowering the priority given that it's not a new bug triggered by new aliases. I also forgot to mention that this was reported by @the-nurk on Slack.
I support this mainly because, currently, `Err` and `Validate` serve a very similar purpose and they are rather confusing. And with CUE leaning into lazy or optimal evaluation, I think...