Looking at the content of this thread and the (mostly conflicting) requests for new features, one comes to two possible conclusions: either the language is still in its infancy and awaiting a concise definition, or the language is on the verge of a split. Into different branches though.
The core problem with Nim is the mixture of procedure overloading, name mangling (creating problems at its own), unrestricted generics, "static" and "macros". It is e.g. impossible to define concise interfaces. I am agnostic about the future of Nim. It is a like a "unfinished symphony". It could be a "better C" \- like the PL Odin, a project that started in 2015 and matured quickly. Or it could be a language based on coroutines and first class continuations. Or a "Python that compiles". But Nim can't be everything of these at once. What to do next? Perhaps external expertise might help.
