No that's not true.
As soon as you use sequences or strings or async you depend on the GC.
You can however compile with gc:destructors or gc:arc so that those are managed by RAII.
I used various modules with gc:none
I meant that new ARC GC, that will replace the current one, can be used for the kernel.
It's still a GC, technically, but, quoting Araq on ARC:
Nim is getting the "one GC to rule them all". However calling it a GC doesn't do it justice, it's plain old reference counting with optimizations thanks to move semantics.
Also, the new ARC memory manager replaces GC and can run in a kernel.