Yes, the nim compiler outputs C-source code then passes that to your compiler. It can also output other languages. That said while a lot is configurable, I wouldn't consider the generated C as something a human can work on.
Optional garbage collection, with choices on which type of garbage collection.
I wonder how well the Nim standard library handles this. D has been controversial with this because the standard library expected GC to be enabled although allowing it to be disabled. I think this story has improved but it may have hurt adoption as a systems programming language that is now hard to restore.
Sadly this is something that Nim can also improve on. I will actually be looking into getting the stdlib ready for the highly sought after 1.0 release and will be keeping this in mind.
The stdlib not working without GC, making not truly optional, is one of the main reasons I stopped using nim - though I haven't checked if this is better in some time.
What were you planning to develop? This should help me figure out whether the stdlib still has an issue for that use case without a GC.
Embedded code, modules for use in higher level languages - and this is the killer, memory management in "mixed" contexts
Well it works without GC, but memory is never freed :)
Right, I'm sorry, I suffer a narrower definition of "works" :)