Should protection attributes disambiguate?

[Jonathan M Davis]

On 2011-06-20 15:58, Andrej Mitrovic wrote:
> Note that there is a bug with private symbols right now. If you have a
> private class in module A, a public function with the same name in
> module B and a module C that imports them both, the two names will
> clash. I've reported this recently.

That's not necessarily a bug, though we may want to change D's behavior in 
this regard. Making the symbols private makes it so that you can't access 
them, not so that you can't see them. What Peter is asking for is essentially 
that the compiler ignore private symbols when it disambiguates symbols, which 
would fix your bug. But I believe that the behavior that you're seeing is in 
fact what is currently supposed to happen.

- Jonathan M Davis