DIP22 : Private symbol visibility

[Timon Gehr]

On 01/30/2013 10:42 AM, Dicebot wrote:
> ...
> That was the most uneasy part of proposal. I have been thinking for few
> hours about it, considering different options. In the end, I have
> decided that it is only confusing to one coming from C++ lax approach
> and for clean mind it should make perfect sense that private symbol is
> indistinguishable from non-existing one in regular user code - that is
> the point of encapsulation how I get it.
> ...

As long as compile-time reflection cannot get hold of the error message, 
the more helpful diagnostic does not do any harm. (After all, the 
programmer might still be aware of the existence of the member, but 
missing that it is not accessible (yet) from the module he/she is 
currently working on.)