Behavior of opEquals

[Jacob Carlborg via Digitalmars-d]

On 2015-09-05 08:18, Jonathan M Davis wrote:

> There is nothing in the spec about supporting operator overloading with
> free functions, so I don't know where you get the idea that it's even
> intended to be a feature. UFCS applies to functions which use the member
> function call syntax, and operators aren't used that way. There is no
> plan whatsoever to support operator overloading via free functions.

Since "a == b" would be lowered to "a.opEquals(b)" one could argue that 
the compile would also try UFCS since it would do that if the code had 
been "a.opEquals(b)" from the beginning.

-- 
/Jacob Carlborg