[Issue 10037] Compiler should not generate opEquals method implicitly
d-bugmail at puremagic.com
d-bugmail at puremagic.com
Mon May 6 21:19:37 PDT 2013
http://d.puremagic.com/issues/show_bug.cgi?id=10037
Kenji Hara <k.hara.pg at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |3789
--- Comment #1 from Kenji Hara <k.hara.pg at gmail.com> 2013-05-06 21:19:36 PDT ---
Essentially in D, equality operation '==' should probide structural equality.
For built-in basic types, it is just same as bitwise equality. For array types,
'==' provides length and element-wise equality. For AA types, it provides
logical AND of contained elements equality. Then, for any struct types which
does not have explicit opEquals, D should provide member-wise equality.
It has been discussed long time in bug 3789, and I think it should be fixed.
But this issue is an obstacle to fix it.
--
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
More information about the Digitalmars-d-bugs
mailing list