Open mvdan opened 2 months ago
With CUE_EXPERIMENT=toposort
having landed in https://review.gerrithub.io/c/cue-lang/cue/+/1202401, and it working on both evalv2 and evalv3, the need for this debug flag (and the fact that it broke with evalv3) is much less important to us. For example, https://github.com/cue-labs/services/blob/73749476ea5502f98e389160f4e431b6f1ab0806/deploy/baseline.sh#L8-L10 can be moved to using CUE_EXPERIMENT=toposort
, which I will attempt shortly.
Do we want to keep CUE_DEBUG_SORT_ARCS
around, perhaps as part of CUE_DEBUG
instead? If so, we probably need to document it a little better and ensure it works with evalv3. If not, because we think that all end user use cases are resolved by toposort, and it's not really needed for our own debugging anymore, then we should delete it.
cc @mpvl @cuematthew
I would expect the following testscript to succeed:
However, it fails:
evalv3 fails to sort the fields when looping in the list comprehension, so we get a non-sorted result.