http://d.puremagic.com/issues/show_bug.cgi?id=5519
Simen Kjaeraas changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=5519
--- Comment #5 from bearophile_h...@eml.cc 2011-02-04 12:18:18 PST ---
This issue is essentially a dupe of bug 3789
--
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because:
http://d.puremagic.com/issues/show_bug.cgi?id=5519
--- Comment #4 from Denis Derman 2011-02-03 04:30:32 PST
---
One (hopefully last) more point:
A situation where one may constantly need to compare structs for equality (by
value!) is unittests:
unittest {
...
assert (result == S(a, b
http://d.puremagic.com/issues/show_bug.cgi?id=5519
--- Comment #3 from Denis Derman 2011-02-03 03:55:37 PST
---
The core issue, I guess, is that '==' implicitely means comparison "by value
equality". This sense is even more obvious in D which has a dedicated operator
'is' for comparison "by re
http://d.puremagic.com/issues/show_bug.cgi?id=5519
--- Comment #2 from Denis Derman 2011-02-03 03:40:07 PST
---
(In reply to comment #0)
> Surprisingly this works (DMD 2.051):
>
>
> struct Bar {
> int x;
> const bool opEquals(ref const(Bar) o) {
> return x == o.x || x == -o.
http://d.puremagic.com/issues/show_bug.cgi?id=5519
Denis Derman changed:
What|Removed |Added
CC||denis.s...@gmail.com
--- Comment #1 fro
