During my years lurking in the Nim community, I've got the impression that the 
Nim compiler has evolved a lot during the years but sadly hasn't been 
refactored when new big changes have been made, but instead they were added on 
top of the old framework. And this fact of adding ad-hoc solutions upon ad-hoc 
solutions has created a final product that is prone to create bugs when 
introducing new features, which harms the language's evolution. Adding ad-hoc 
solution to fix the bugs introduced due to the ad-hoc nature of the compiler, 
just makes it worse... This is the way I've come to understand it at least.

So to my point: what better time to rewrite the compiler from the ground up, 
than for a major release. (whether it is Nim 2.0 or Nim 3.0 doesn't matter that 
much). The major thing is that it should happen before too much damage has been 
done, making the rewrite a truly painful experience...

I know this isn't a flashy new feature, and it will be boring as heck to do, 
but it will be necessary at some point in the future. The sooner the better.

Nim 2.0 - Nim rebuilt from the ground up, stable and ready to take the world by 
storm for real

Reply via email to