On 09/23/2014 10:19 PM, monarch_dodra wrote:
As I said, local imports, IMO, should behave in all aspects as a global import. It simply only exists during its scope, but is not actually any more "internal" than the rest. If a local import creates a symbol ambiguity, then it's ambiguous, and compilation ceases. I think that's the behavior we should be going for.
I have previously suggested to first look up symbols in local scopes, and only if no match is found within the current module, all imports that are in visible scopes are considered. I think this has the effect you are after. Is this what you are proposing?
