https://issues.dlang.org/show_bug.cgi?id=11161
Dlang Bot changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.dlang.org/show_bug.cgi?id=11161
Dlang Bot changed:
What|Removed |Added
Keywords||pull
--- Comment #9 from Dlang Bot ---
https://issues.dlang.org/show_bug.cgi?id=11161
RazvanN changed:
What|Removed |Added
CC||razvan.nitu1...@gmail.com
--- Comment #8 from
https://d.puremagic.com/issues/show_bug.cgi?id=11161
timon.g...@gmx.ch changed:
What|Removed |Added
CC||timon.g...@gmx.ch
--- Comment #7
http://d.puremagic.com/issues/show_bug.cgi?id=11161
Denis Shelomovskij verylonglogin@gmail.com changed:
What|Removed |Added
Severity|normal |major
http://d.puremagic.com/issues/show_bug.cgi?id=11161
--- Comment #5 from monarchdo...@gmail.com 2013-10-06 01:18:48 PDT ---
(In reply to comment #2)
For the expression `t1 != t2`, the semantic analysis is done in the following
order:
1. Find opEquals method from the type of operands
2. If
http://d.puremagic.com/issues/show_bug.cgi?id=11161
Kenji Hara k.hara...@gmail.com changed:
What|Removed |Added
Keywords|wrong-code |spec
http://d.puremagic.com/issues/show_bug.cgi?id=11161
--- Comment #3 from Kenji Hara k.hara...@gmail.com 2013-10-03 02:53:07 PDT ---
(In reply to comment #1)
I would expect that alias this would have zero effect on == save for when
comparing with a value of the type that's being aliased instead
http://d.puremagic.com/issues/show_bug.cgi?id=11161
--- Comment #4 from Jonathan M Davis jmdavisp...@gmx.com 2013-10-03 10:55:48
PDT ---
'alias this' should be considered for operator overloading. If not, sub-typing
by using 'alias this' won't work anymore.
I would expect sub-typing via
