opCmp, [partial/total/pre]orders, custom floating point types etc.

[tsbockman via Digitalmars-d]

On Wednesday, 13 January 2016 at 00:31:48 UTC, Andrei 
Alexandrescu wrote:
> I'd leave it to a named function. Using the built-in comparison 
> for exotic orderings is bound to confuse users. BTW not sure 
> you know, but D used to have a number of floating point 
> operators like !<>=. Even those didn't help. -- Andrei

Although I would have use for "exotic orderings" in some of my 
own code, I think this is the right decision.

Really the only reason I'm tempted to say they should be allowed, 
is to smooth interaction with floating-point. But, I think what 
that really means is that the design of the floating-point 
comparisons is bad. (Which is not D's fault, I know.)