And as we've already discussed "using" are ugly and in my opinion only make sense in the REPL. But well, that's my opinion and I'm not a language designer.
Just try to "using" a module redefining "sin", you won't try twice. I'm also waiting for the first julia big projects and users begging "would it be possible to provide developer documentation on module Foo.jl? It's so big and intricated that I can't figure out what is used and when." Wouldn't that make sense to allow only imports of exported functions? What's the rational of the consenting adult approach? Wouldn't it be possible to do things a la Python with the double underscore: mymod.__foo is not directly accessable, o e has to access it via mymod.__mymod_foo. Exported object could be accessable as they are and non exported object could be accessable through mymod.NotExported for instance.
