The way custom comparisons are currently implemented force you to always return an integer and doesn't tell you what operation you are doing.
An example of how it can bite is that mir can't do elementwise comparisons similar to how it does addition or multiplication since it has to return an int for comparisons.
So a + a == [2, 2, 2] and a * a == [1, 1, 1] but you can't express a < a == [false, false, false].
I get the logic of only making the user create a single comparison function but maybe a possible fix would be to check if there is an opBinary for the relevant comparison operator before doing the usual opCmp logic.
Comment #1 by robert.schadek — 2024-12-13T18:52:55Z