[Issue 6036] Constructor, static opCall and object opCall

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=6036



--- Comment #14 from bearophile_hugs at eml.cc 2012-10-07 05:51:58 PDT ---
(In reply to comment #12)

> It is still a corner case of language spec, but I think it is an expected
> behavior.
> Because, the operator overloading mechanism just consider whether the function
> named opXXXX exists or not, and doesn't consider whether the opXXXX is really
> static or not.

See a discussion thread:
http://forum.dlang.org/thread/rwypxtvosdhjiwrtzwfi@forum.dlang.org

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------