DIP16: Transparently substitute module with package

[Jacob Carlborg]

On 2012-04-04 18:33, Michel Fortin wrote:

> You might think I'm trying to split hair in four to find flaws, that no
> one is going to do things that dumb, but I unfortunately think the
> problematic pattern is already quite common. How many times have we seen
> modules containing a class, variable, or function having the same name
> as the module's name? What should happen when you publicly import those
> modules in the package.d file?

I do that all the time in my libraries.

-- 
/Jacob Carlborg