Marcel van Lohuizen

FTR: to me `1m` reads as a duration value, meaning 1 minute.

-l is defined for making non-cue into a single cue namespace. It was not designed with transformations in mind. This could be considered given enough use cases and how this...

To do actual transformations, I could imagine using the `-e` flag in combination with the query proposal to generate arbitrary transformed output.

> With the `-e` flag, is there any way of referencing the top level object currently? There is not currently. But the `-e` flag would then use whatever convention used...

The default assumption for APIs in Go is that they are not goroutine safe unless explicitly mentioned. But some are, in fact goroutine safe. Other than that, I would phrase...

It seems that evalv3 is doing the right thing: ``` if X.oneOrTwo.two.optional == _|_ { optional: "optional set" } ``` Basically, this condition tests that a value is "undefined", but...

An even nicer way to write it would be: ``` out: #Application & { oneOrTwo: two: {} } #Application: { oneOrTwo: #OneOrTwo oneOrTwo: *_appDefaults[_kind] | _ _kind: oneOrTwo.kind } _appDefaults:...

I made an error in the above example. Of course I need to repeat the two field. That still doesn't fix it, as the closedness algo does not resolve the...

Note, I've made this pattern now work in evalv3: ``` out: #Application & { oneOrTwo: two: {} } #Application: { oneOrTwo: #OneOrTwo oneOrTwo: *_appDefaults[_kind] | _ _kind: oneOrTwo.kind } _appDefaults:...

To update on the progress of the development of the new evaluator, a critical component of making performance improvements in CUE. The [Evaluator Roadmap project](https://github.com/orgs/cue-lang/projects/18) is gradually being filled out...