best way to handle UFCS with ambiguous names: using std.typetuple.Alias!

[John Colvin]

On Monday, 10 June 2013 at 02:02:09 UTC, Timothee Cour wrote:
> UFCS chains are problematic when a symbol is ambiguous (eg 
> after import
> std.stdio:write;import std.file:write);
>
> I previously suggested to add the syntax
> 'arg1.(std.file.write)(arg2)'
> (see 'support UFCS with fully qualified function names (was in
> "digitalmars.D.learn")'  to avoid breaking UFCS chains.

We should allow this anyway, simply to deal with static imports.