So, coffeepot, if I understood correctly, your suggestion is: * Anyone just write their code as they wish without caring just as they do today. * Before saving the code to disk, some mechanism automatically transforms the code to add namespaces back (basically). That code is still valid Nim and the conversion could be tweaked with rules so that _readability_ of the raw file is really enhanced (as you said, "just" adding namespaces does not equate that). * Before loading the code from disk, the mechanism could be reversed.
As long as this mechanism is widely used in the community, I like the idea. The concept of rules (that may possibly be tweaked) is also great as it would allow people to choose what they want displayed as opposed to what others forced onto them. In that sense such a tool could become even more powerful than go-fmt! For this to work reliably, one may need to work at the AST level which has the extra advantage of standardising what's written on disk (like what go does with go-fmt). From the outside, the code would seem pretty standardized which is always nice, especially in larger teams. But at the same time, once **in** your IDE, the code would look like what **you** prefer (_unlike_ what go-fmt currently does).
