Re: Thoughts on imports

[GULPF]

It might look useful for simple cases, but what happens when you want to import 
an operator? Or if you want to import a hash procedure that the `tables` module 
should have access to? Using a macro like that will just be an uphill battle 
and shouldn't be encouraged. The "import everything into scope"-style of 
imports that Nim uses has some limited issues but it's deeply ingrained into 
the language.