Daniel Martí

Very much related: `cue fmt` should probably transform e.g. `true: true` into `"true": true` for the sake of clarity, even if we continue allowing `true: true` to be valid. See...

This is resolved as of v0.15.0; I bisected the fix to a1cfb1ca4e750db0925510ac35b3433eae768064. I'll close this with a test.

I have reduced this to a self-contained and relatively small testscript, which reproduces the panic as of 4cbb1800466b0202d6468b1ad5a4836ebb4c7d72, and shows that it's an evalv3 regression: ``` env CUE_EXPERIMENT=evalv3=0 exec cue...

FYI edited the original post as it conflated `-l '#schema'` with `-l '#schema:'`.

Reduced it further to a `cue def` evalv3 regression: ``` # evalv2 env CUE_EXPERIMENT=evalv3=0 exec cue def # evalv3 env CUE_EXPERIMENT=evalv3=1 exec cue def -- input.cue -- package p #recursive:...

This appears resolved as of v0.15.0; I bisected the fix to ab40e7f72cd12dfc06f62032ca7e8d6eb4ae7adc. I'll close this with a regression test.

This issue is about two feature requests - Marshaller+Unmarshaller interfaces, and then better struct tags to add features to the marshalling and unmarshalling. Just so I understand better - do...

My understanding is similar. We already have some form of encode options, but we have no decode options. Whatever interfaces we add for custom marshal/unmarshal on types, those must leave...

Note https://github.com/cue-lang/cue/issues/1630 as well, which is related.

Go has done this now with an "ignore" directive in `go.mod`: https://github.com/golang/go/issues/42965 I would suggest that we consider the same approach - either an include or an exclude list in...