[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

https://issues.dlang.org/show_bug.cgi?id=6579 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

https://issues.dlang.org/show_bug.cgi?id=6579 --- Comment #10 from Steven Schveighoffer --- This is a pretty old issue, and I'm not sure it's super-important. But to answer your question, the idea would be for the type to opt-in on having a static function be considered

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

https://issues.dlang.org/show_bug.cgi?id=6579 --- Comment #9 from anonymous4 --- Dunno, this would complicate the language and lower its usability without a clear problem and gain. How would code then decide whether to call instance.method() or

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

https://issues.dlang.org/show_bug.cgi?id=6579 Mike Franklin changed: What|Removed |Added See Also|

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

https://issues.dlang.org/show_bug.cgi?id=6579 Mike Franklin changed: What|Removed |Added See Also|

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

https://issues.dlang.org/show_bug.cgi?id=6579 Alex changed: What|Removed |Added CC||sascha.or...@gmail.com --

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

https://issues.dlang.org/show_bug.cgi?id=6579 hst...@quickfur.ath.cx changed: What|Removed |Added CC||hst...@quickfur.ath.cx --

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

http://d.puremagic.com/issues/show_bug.cgi?id=6579 --- Comment #8 from Steven Schveighoffer schvei...@yahoo.com 2012-06-04 10:01:16 PDT --- (In reply to comment #7) Oh, and i just noticed the suggestion in this report that static fields should not be accessible via an instance - no, that

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

http://d.puremagic.com/issues/show_bug.cgi?id=6579 Gor Gyolchanyan g...@boloneum.com changed: What|Removed |Added CC||g...@boloneum.com

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

http://d.puremagic.com/issues/show_bug.cgi?id=6579 --- Comment #5 from art.08...@gmail.com 2012-06-03 06:42:55 PDT --- (In reply to comment #4) It hinders overloading. For so long I wanted to be able to have both static and non-static opDispatch and opCall and couldn't because of this.

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

http://d.puremagic.com/issues/show_bug.cgi?id=6579 timon.g...@gmx.ch changed: What|Removed |Added CC||timon.g...@gmx.ch --- Comment #6

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

http://d.puremagic.com/issues/show_bug.cgi?id=6579 --- Comment #7 from art.08...@gmail.com 2012-06-03 07:54:14 PDT --- (In reply to comment #6) Slightly refining the overloading rules as proposed in issue 3345 would already solve the problem. struct T{ static void foo(){...}

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

http://d.puremagic.com/issues/show_bug.cgi?id=6579 art.08...@gmail.com changed: What|Removed |Added CC||art.08...@gmail.com --- Comment

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

http://d.puremagic.com/issues/show_bug.cgi?id=6579 Steven Schveighoffer schvei...@yahoo.com changed: What|Removed |Added Summary|Calling static method |Calling