Intended behavior or bug (private vs public static)

[Andre via Digitalmars-d-learn]

Thanks a lot. I will create a bug report.

Kind regards
André


On Friday, 7 November 2014 at 06:09:02 UTC, Jonathan M Davis via 
Digitalmars-d-learn wrote:

> That looks like a bug. All you have to do is change the order 
> of the two
> function declarations or rename the non-static one to something 
> else, and it
> compiles. So, somehow, the fact that the non-static one has the 
> same name as
> the static one and the fact that it comes first screws up 
> accessing the
> static one. And explicitly marking the static one as public 
> doesn't help.
> So, you should report is a compiler bug:
>
> https://issues.dlang.org
>
> - Jonathan M Davis