Equivalence and comparability

jpluscplusm commented 7 months ago

We don't currently explicitly document how CUE treat fields/lists/structs when comparing them. We should write a piece of documentation that explains this, including elements that address:

the concept of comparison vs subsumption
what "equivalence" means in CUE, currently, and how this is anticipated to change in the future
how/if concrete and noncrete values are comparable and/or equal

A concept guide feels suitable for this piece, but we should also consider placing a section inside the Language Guide.

myitcv commented 7 months ago

If this isn't sufficiently covered in the spec we should also raise an issue in https://github.com/cue-lang/cue

jpluscplusm commented 7 months ago

If this isn't sufficiently covered in the spec we should also raise an issue in https://github.com/cue-lang/cue

I've raised https://github.com/cue-lang/cue/issues/2779, which is tightly coupled to the explicit mention in list.Contains' documentation that its second argument must be comparable.

I believe that in conjunction with the existing issues https://github.com/cue-lang/cue/issues/2583, https://github.com/cue-lang/cue/issues/2027, https://github.com/cue-lang/cue/issues/2026, and https://github.com/cue-lang/cue/issues/2024, there's enough coverage of any gap between the spec and the implementation.

cue-lang / docs-and-content

Equivalence and comparability #49