[Issue 11845] selective (and renamed) imports clash with local symbols

[d-bugmail at puremagic.com]

https://d.puremagic.com/issues/show_bug.cgi?id=11845



--- Comment #2 from monarchdodra at gmail.com 2013-12-31 14:16:35 PST ---
(In reply to comment #1)
> This is the way it is designed to work, it is not a bug.

I'd understand an *ambiguity*, but a straight up conflict? It basically means
that if I need to import a specific symbol in a module, I'm *banned* from
declaring an *overload* myself?

That seems strange, since simply declaring all the functions in the same module
remains legal. The functions are *mutually* exclusive. Technically, there isn't
even any ambiduity :/

In particular, in my original report, I did a *renamed* import: From my
module's point of view, there is only "foo". Why is "splitter" conflicting with
"foo"?

> Altering this behavior
> will, of course, potentially break significant existing code.

I challenge you to come up with an example where this would break existing
code. I don't see it.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------