Daniel Martí

As Roger said in the last comment, this is a potentially breaking change that we want to do carefully in an alpha release, so I've pushed it back slightly to...

On one hand we're limited by the encoding/json API, since it doesn't allow reusing buffers in any way. On the other hand, most of this is our own fault, since...

Friendly nudge @lujiajing1126 - what would you expect the OpenAPI output here to be?

I've brought up the same to Marcel in the past, this would indeed be nice to have. We just have to be careful to clearly document that the structure of...

Also to add a bit of clarification: this needs some design to decide if the stats should be collected... 1) globally; probably not, as that would not mesh well with...

For the sake of tracking this work better, let's use https://github.com/cue-lang/cue/issues/2856 going forward. I've added all relevant info there now.

@imax9000 is correct that this is unrelated to empty structs. Below is a reproducer using a definition and a separate struct, for extra clarity: ``` # evalv2 env CUE_EXPERIMENT=evalv3=0 exec...

In the meantime, the workaround is to separate the unification into another field, such that it's not inline: ``` #Schema: { allowed?: int } data: { disallowed: 123 } _unified:...

Briefly spoke with @mpvl and we both agree that this should fail. The fix from late 2022 was probably a bit too agressive in dealing with inline structs. The workaround...

I've left a potential fix for @mpvl at https://cue.gerrithub.io/c/cue-lang/cue/+/1224395. It's not complete, as one test fails, and I'm not sure it's entirely correct.