DIP16: Transparently substitute module with package

[Steven Schveighoffer]

On Thu, 05 Apr 2012 10:26:16 -0400, deadalnix <deadalnix at gmail.com> wrote:

> Le 05/04/2012 14:58, Steven Schveighoffer a écrit :
>> On Thu, 05 Apr 2012 08:49:24 -0400, deadalnix <deadalnix at gmail.com>  
>> wrote:
>>
>>> Le 05/04/2012 13:46, Steven Schveighoffer a écrit :
>> No, public imports simply mean that you can view the publicly imported
>> module. It does *not* add aliases to the importing module.

[snip]

> I know. I think you answered too fast.
>
> I wasn't stating that public import are the same as what you propose. I  
> was discussing the fact that both probably answer the same need and that  
> 2 different syntax is something to avoid.
>
> Code wouldn't be broken in unexpected way, because thing will cause  
> either a compile error (collision of names, but the problem exists with  
> other solutions too) or is illegal in the current shape of the language.

My assertion above is 100% *WRONG*.  See this bug I just filed.   
http://d.puremagic.com/issues/show_bug.cgi?id=7830

In fact public imports today are *exactly* the same as what I proposed. I  
had no idea.

I think we are (well, at least I am) on a wild goose chase here.  All that  
is left to discuss is if/how we want to allow importing of packages.

But I think DIP15 already covers that  
http://prowiki.org/wiki4d/wiki.cgi?LanguageDevel/DIPs/DIP15

I think DIP16 is worksforme/invalid, and should be closed.

-Steve