[Issue 2028] Can't create template class in module of same name

[Jarrett Billingsley]

<d-bugmail at puremagic.com> wrote in message 
news:fur052$309q$1 at digitalmars.com...
> http://d.puremagic.com/issues/show_bug.cgi?id=2028
>
>
>
>
>
> ------- Comment #2 from wbaxter at gmail.com  2008-04-24 17:04 -------
> (In reply to comment #1)
>> I don't know whether to call this a bug or a language design issue, but I 
>> know
>> the workaround: specify the full name
>>
>> Use
>>     a.a
>> instead of
>>     a
>>
>
> I think this can also be avoided by having the module in a package.  Then 
> DMD
> seems not to get confused.  I've not totally understood the specifics, it 
> seems
> modules and other symbols conflict in ways that package names don't.
>
> So I think if you put a.d into an 'a' directory, make it's module 
> statement be
> "module a.a;" then do
>
> import a.a;
>
> then you won't get the conflict.  Can anyone confirm this?  Don't have 
> time at
> the moment...

That wouldn't work either, since the top-level name is also a.  It's that 
modules and packages have a higher precedence than the symbols within them.