Daniel Martí

That's it for now. We still have some performance and memory usage work to be done on evalv3, so that's still our focus for issues like this one.

Don't spend energy reducing that one "field not allowed" error, as we are aware of regressions in that space: https://github.com/cue-lang/cue/issues/3601 We are going to continue with the performance work once...

Seems similar to https://github.com/mvdan/sh/issues/1041, thanks for reporting.

Slightly smaller repro: ``` exec cue export -e 'obj2.name' in.cue cmp stdout stdout.golden -- in.cue -- obj: this={ (#makeName & {enable: this._enable}).out } obj: _enable: true obj2: obj #makeName: {...

@nxcc thanks for following up here! We will add a regression test to mark this issue as closed then.

For the record, I think most people would want a feed of "news", such as when we announce a new alpha release, or when we post a new upcoming event...

I think we might get this for free via BlueSky; every public account, including ours, has an RSS feed. In particular: https://bsky.app/profile/did:plc:gcwkuuf3dygnewyce2onfvb5/rss Our BlueSky account is effectively a feed of...

Feel free to send a PR with a test.

Would this be driven only by a heuristic, or also via some option?

We always use the new YAML decoder as of v0.10.0, based on the latest go-yaml: https://github.com/cue-lang/cue/issues/3027 And, from what I can see, we already do use multi-line YAML strings when...