Proposal: Make imports private by default

[Stewart Gordon]

Bruno Medeiros wrote:
> Following the recent generalized discussion about imports, and the entry 
> in the wiki of proposals of new kinds of imports, and also the idea I've 
> mentioned before of using the wiki to keep track of proposals, I have 
> launched this thread as the primary point of discussion for a very well 
> known and familiar proposal:
> 
> == Make imports private by default ==
> 
> -- Description --
> All import statements which do not have a "protection" attribute should 
> default to private, instead of public.
<snip>

It would strike me as inconsistent, considering that everything else is 
public by default.  Moreover, I can imagine that people would begin to 
ask for a keyword to reset protection to the default, if not for 
practical use then for the sake of completeness.

Stewart.