> What you said about cyclic imports is so true. In many ways, Nim tries to be > a low-friction language, and it succeeds in making a lot of things easy that > are hard in other languages. This, however, is in stark contrast to how hard > it is to properly organize types and functions across files in Nim.
Of course, automatic cyclic imports resolution would be nice to have -- no doubt about it. But it is not a show stopper for large projects. In C/C++ world there is no cyclic dependencies resolution either and forward declarations are required like in Nim. Yet there are many successful large and huge C/C++ code bases around. \--Leo| ---|---
