Add string singleton comparison operators to scala.compiletime.ops.string. #24748
Conversation
…ring. The numeric singleton types already have comparison operators, but for some reason this was still missing for singleton String types. This enables a lot of potential valuable type-level computations, but one in particular is the ability to sort a named tuple, which means that if you're commonly adding/removing entries from a named tuple, this provides a way to normalize them, so two named tuples that were constructed in a different order can still be treated as equivalent types.
wtetzner
force-pushed
the
string-singleton-comparisons
branch
from
881ae82 to
f5d3a15
Compare
|
i wonder if its generally useful to also have tuple sorting itself as a type operation - perhaps it can have a binary op "comparator" argument as well (so |
|
not sure this makes sense: there is no single lexicographic order for strings, this always depends on the locale. |
Are you sure? I don't think Java's default String comparison depends on locale, and I believe that's what Scala's comparison operators use. It's case folding that needs locale, and we're not doing that here. I think you need to use |
3 participants
The numeric singleton types already have comparison operators, but for some reason this was still missing for singleton String types.
This enables a lot of potential valuable type-level computations, but one in particular is the ability to sort a named tuple, which means that if you're commonly adding/removing entries from a named tuple, this provides a way to normalize them, so two named tuples that were constructed in a different order can still be treated as equivalent types.
Test results: https://gist.github.com/wtetzner/6f38842c5d06a5d70ba5eea2cf7ce298