Paul Jolly

@takonomura I see. I have replied in https://github.com/cue-lang/cue/issues/3142#issuecomment-2708228748. Happy to help move forward getting something added to the standard library if we can agree on a sensible API.

I suspect this is a duplicated of https://github.com/cue-lang/cue/issues/4037

@errordeveloper - apologies, I missed this issue when you first created it. @grantzvolsky - thanks for the follow up which caused me to see it. Incidentally, @mpvl's reference to a...

> however it's wont be before one created `cue.mod/module.cue` and set the import path there, right? Correct. I'm not sure `cue get go` makes sense in a context without a...

Providing a specific example from the GitHub actions world: ``` ! exec cue vet -c -d '#Workflow' cue.dev/x/[email protected] x.yaml cmp stderr stderr.golden -- x.yaml -- name: Go on: pull_request: branches:...

> It would be nice to have an example where the discriminator is perfect It might be nice, I agree, but this is the reality of a popular configuration.

Just noting our offline conversation last week regarding the "imperfect discriminator". My thesis was: * We have to make progress in this space because currently error messages are not manageable...

Adding comments from a discussion with @rogpeppe - `-T` is currently fairly benign in terms of the values injected. There is nothing "sensitive" per se. Environment variables can contain sensitive...

That's an interesting observation, @Djaytan. Please correct me if I'm wrong, but I think what you're proposing could be built on top of my idea? However, what you're proposing is...

Marking as v0.8.0 and "Needs fix" - not because it's a bug, rather more a TODO per @mpvl. Because we've indicated in the spec that we will support this, but...