--- Comment #2 from Leandro Lucarella <> 2009-11-14 09:20:25 
PST ---
(In reply to comment #1)
> Maybe something like this could be allowed to mean "import renamed to the
> leaf":
>     import (;
> Sometimes I do want the actually fully qualified name, like for a module like
> std.string.  Having "string" mucks with the type "string".  Or maybe parens
> around the part to keep:
>     import;

I think it's very unfortunate to have a module with the same name of an almost
built-in type. Maybe the module can be renamed to std.str; or we can live with:

import str = std.string;

Another possibility is, if bug 3503 gets implemented, is to leave static import
untouched. I think that's even a good idea for backwards compatibility.

static import std.string;
import std.algorithm;;

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to