Hello,
Interesting by this language I wish to have more information before committing myself :
Thank you
I was able to read on the web efficient garbage collector offers you, it's fine but is it possible to use it without... in the manner of Rust for example ?
Nim is GC by default - which is the way to go for the vast majority of cases, and most people who think they need manual memory control actually don't.
Most of Nim's standard library and other modules require GC. You can turn it off, but "here be dragons" - you'd have to patch any modules you need that don't yet work without GC (for which we would be grateful).
I was able to read on the web efficient garbage collector offers you, it's fine but is it possible to use it without... in the manner of Rust for example ?
Nim has option --gc:none if you need to manage memory manually.
writetracking and destructor is good reading on how Nim trying tackle memory management safety.
This thread is an example of achieving compatibility between C++ and Nim which needed in real-time processing
Is it still worth investing in the book NIM IN ACTION where it is better to wait for a next issue ?
It's worth investing now, we are going to ensure that v1 is compatible with the book :)
Nim is GC by default - which is the way to go for the vast majority of cases, and most people who think they need manual memory control actually don't.
Most of Nim's standard library and other modules require GC. You can turn it off, but "here be dragons" - you'd have to patch any modules you need that don't yet work without GC (for which we would be grateful).
Indeed, people seem to be really GC allergic, even though they don't have to be bad.
Nim isn't Java where every object is GC collected. The GC also isn't completely intransparent(https://nim-lang.org/docs/gc.html ). And if you really need non GC'ed memory you can always allocate some additionally.
Thank you for your feedback ;)
I will buy the book and started to enter the universe of NIM ^^