http://d.puremagic.com/issues/show_bug.cgi?id=6180
--- Comment #11 from timon.g...@gmx.ch 2012-09-05 18:49:03 PDT --- (In reply to comment #10) > > It shouldn't be. The summary obviously describes horribly broken behaviour. > > It describes how it works in C++ Irrelevant. > which is exactly how it works in D. It's that way by design, This does not matter either. It is an incorrect design. > and anything else would require that the language be changed. > > What many have argued for is that private symbols should be hidden (or at > least > not be considered in overload resolution when not accessible or otherwise > cause > conflicts with accessible symbols), which I think would be a major > improvement, These are not conflicts. The compiler is deliberately lying about this. > but that's not the way that it currently works or is ever expected to work > unless you can convince Walter to change it. Introducing a private module scope symbol currently is a breaking interface change (even in code that does not use any metaprogramming!) This is ridiculous. I assume that Walter will figure it out. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
