Re: Some problems with operator overloading

[Trass3r]

I can see one potential reason to use opBinary("==") and that is to  
collect binary operator code in one place.

Currently dmd checks that and turns == into opEquals, should never become  
opBinary!("==")