On 2/12/12 7:28 PM, Martin Nowak wrote:
The shallow distinction of visibility vs. accessibility breaks the
module system because
one can't safely add a private symbol without possibly affecting every
dependent module.
Thus we're back at using underscore names to protect from that.

Yes, and this is exactly why I argued to disregard invisible symbols during overload resolution in the past. Walter seems to be firmly convinced that the current solution is the right thing to do, but I can't recall what his reasons were.

David

Reply via email to