Marcel van Lohuizen
Marcel van Lohuizen
We let our performance update coincide with our community call. There are some big updates since last time. We now have the `evalv3` enabled by default in our v0.13 alpha....
Since our last update, we’ve made continued progress on stabilizing and improving `evalv3`, which is now the default in `v0.13`. This marks a significant milestone in the development effort. While...
It has been a while since we posted our last performance update. We have shifted from focussing on specific known algorithmic improvements to focussing on specific issues reported by users...
Makes a lot of sense. One alternative API is to export comments when used with `def`. I'm surprised that `cue def --out yaml` doesn't already export comments, actually.
@cuematthew why would you say you're pretty sure this is not a structural cycle? Without cycle detection, it would clearly terminate, but that does not mean it is not a...
If this usage pattern is prevalent, which I suspect it is, we should provide some easier transform mechanism. ``` let T = transform x { {...} => for k, v...
In the meantime, you could write something like this: ``` #makeOptionalFields: { _in: {...} for k, v in _in { (k): { if (v&{}) != _|_ { #makeOptionalFields & {_in:...
#s is closed, so that is why it reports an error. We could argue whether it should be, but this is how things are supposed to work at the moment.
Observation: v3 does the right thing here.
Changing the behavior is a breaking change for people that include `cue vet` in scripts. This should be gauged on a tooling version, experiment, or such. But I think we...