Import concerns revisited

[David Medlock]

Walter Bright wrote:
> John Reimer wrote:
> 
>> I've seen this error also on several occasions.  I can't remember the 
>> exact source of it, but I think it's related to another issue.  It was 
>> my understanding that that was due to public imports somewhere up the 
>> line. This might have been one of the reasons why discussions started 
>> concerning a borked import system.  Perhaps I'm wrong?
> 
> 
> How imports work is that first a name is searched for in the current 
> namespace. If it is not found, then it is looked for in the import list. 
> If it is found uniquely among the imports, then that is used. If it is 
> in more than one import, an error occurs:

That is not how aliases currently work, just a friendly reminder.
-DavidM