On Tuesday, 23 April 2013 at 04:58:30 UTC, anonymous wrote:
For fast bitwise comparison there's the "is" operator.
The "==" operator should be "slow".
See also http://d.puremagic.com/issues/show_bug.cgi?id=3789

Well okay. The docs will have to be updated for this issue if it's "fixed".

For instance:
http://dlang.org/ctod.html#structcmp

In any case, I stand by that if you have a particular definition of behavior, you should provide it instead of expecting it to "just work." But I suppose using "is" is more appropriate for this type of behavior. But calling it "broken" is a bit too strong.

Reply via email to