Paul Jolly

@takonomura thanks for raising this. We are extremely busy in the run up to [KubeCon](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/) so please bear with us!

Thanks for the reminder @takonomura - I have asked @rogpeppe for thoughts on the API here.

> Given that module paths are canonicalized in many places in the code, it might be hard to avoid mentioning `@v0` in all error messages. Presumably we don't just drop...

I should perhaps have been "softer" in my original description: "for some variation of the error message". The main thing I am suggesting we solve for here is that we...

Hi @joeriddles and welcome to CUE! Reworking your example slightly as a [standalone reproduction](https://github.com/cue-lang/cue/wiki/Creating-test-or-performance-reproducers): ``` exec cue import -l title jsonschema: input cmp input.cue input.cue.golden -- input -- {"$schema": "http://json-schema.org/draft-07/schema",...

Adding some further context to this point following an exchange with @b4nst. Consider: https://cuelang.org/play/?id=aZFUanhM79y#w=function&i=cue&f=eval&o=cue ``` x: 30*1*8000/0.65 x: 48000/13 ``` With v0.0.0-20240503105822-dff77a6d2a5a this gives: ``` x: conflicting values 3692.307692307692307692307692307692 and...

> The inner cycle in `#TimeSpan` is probably what makes it being evaluated twice, but it's difficult for a non experienced user to understand why it's happening. Whatever the cause,...

> This approach would favour "intent in code" I'd tend to agree with that as a guiding approach. Because it feels to me like `float` leaks too much through from...

Thanks @rogpeppe — that’s an interesting angle. I can definitely see that allowing approximate unification of floats could be useful in pragmatic situations, particularly when resolving cycles — and it...

Thanks for raising @verdverm. Yes, could absolutely have a more manual "evaluate" button, equally we could debounce changes, and only process changes after a `Xms` delay.