importing modules with non-identifier names

[Christopher Wright]

yigal chripun wrote:
> This tight mapping is also a problem when you want to rearange physical structure without affecting the API -  e.g. a module had grown to be too big and you want to split it into multiple files. std.algorithm is a prime example of such way too big module. 

What about public imports? Tango does this. The old import will contain 
a pragma(msg) telling you what you should import instead, and maybe some 
aliases in case some functions or types changed names as well.