Nim programming language finally hit 1.0

IGotD- nise at
Wed Oct 9 13:52:18 UTC 2019

One Achilles heel of Nim is that it compiles via C or C++. This 
means in a debugging environment you will be watching the 
environment of the intermediate language. There workarounds for 
this described here.

However, this doesn't solve everything. Also all the variable are 
intermixed with generated symbols, probably with some ugly hash 
added to it. Languages that directly compiles to the target like 
D will give a better debugging environment.

There is a attempt make Nim compile via LLVM instead.

not sure if it is in any productive state yet. Also Nim seems to 
allow C to intermix and all sorts of built in C features that 
will not work when going via LLVM. Trying to merge Nim with C 
features is a bad decision in my opinion.

More information about the Digitalmars-d mailing list