We don't need 800 kinds

[LilithHafner]

"even Claire said so" –@C424

These don't all need different kinds:

...
        "⥺"
        "⭇"
        "⭈"
        "⭉"
        "⭊"
        "⭋"
        "⭌"
        "￩"
        "￫"
        "⇜"
        "⇝"
        "↜"
        "↝"
        "↩"
        "↪"
...

[ShalokShalom]

So.. remove some of them?
All?
Whats the purpose of this issue?

[LilithHafner]

Seems reasonable to have one kind per precedence level, or even one kind for all standard infix operators.
I filed this issue to log some technical debt/code smell. It would be nice to clean this up.

[c42f]

Having mentioned this elsewhere I thought I'd expand just a little on the design we were discussing when this was originally written.

Distinct Kinds are only really useful to the extent that they impact parsing. The only way that operators generally impact parsing is through their precedence classes. (All except for a few specific operator kinds which are treated specially during parsing, such as K"+" for parse_with_chains().)

So we can get away with very few kinds for operators - at max we need one Kind per precedence class plus one kind per special operator type.

If we want to go even further, it may even be possible to reduce all operators to K"Identifier" and emit the precedence class into the numeric flags. Then there's no more remap_kind for operators which could neaten a few things up in the parser.