It's entirely possible to define types and functions in different modules with the same identifiers. An intelligent compiler could look at the context in which they are used and decide which module to use, this is not guarenteed to work 100% of the time though.
I personally think such a feature is unneccesary. But I would say that, I'm the type that uses superstrict, won't use variable tags and resent the fact that when I import a module it will also import any externally referenced modules into my namespace without my say-so. Such a feature would have to be optional or I'd be very unhappy.
This sort of thing makes things like IDE's harder to build as you effectively have to replicate the behaviour in your source parser and makes things like code-completion uneccesarily complex. And for what? The sake of a few Import statements at the top of your code?
However, considering Blitz's heritage I respect the fact it needs to be accesible to a broad userbase.
I personally think such a feature is unneccesary. But I would say that, I'm the type that uses superstrict, won't use variable tags and resent the fact that when I import a module it will also import any externally referenced modules into my namespace without my say-so. Such a feature would have to be optional or I'd be very unhappy.
This sort of thing makes things like IDE's harder to build as you effectively have to replicate the behaviour in your source parser and makes things like code-completion uneccesarily complex. And for what? The sake of a few Import statements at the top of your code?
However, considering Blitz's heritage I respect the fact it needs to be accesible to a broad userbase.