Annoying module name / typename conflict

[kdevel via Digitalmars-d]

On Monday, 2 April 2012 at 22:20:13 UTC, bearophile wrote:

> For DMD choosing one or the other is arbitrary. It's a defect 
> of the way the D module system is designed.

Ran into that problem with a Module S containing

    module S;
    import std.stdio;
    struct S {
       this (string s)
       {
          writeln ("S: " ~ s);
       }
    }

This code

     // auto s1 = S("X"); // useS.d(6): Error: function expected 
before (), not module S of type void

would not compile while

    S s3 = "X"; // OK

works. Has this issue been filed in bugzilla?