No worries, any kind of reply is greatly appreciated as it looks like the number of people interested in hot loading their nim code is rather limited (while to me it's like THE feature).
After you had implemented the hot loading on which your article is based, have you used it in a project and battle tested it a bit? I ask because the moment you do allocations (e.g. system.add, tables.`[]=`, ...) in the hot loaded code, you should've experienced occasional SIGSEGV crashes. Apparently this is caused by the runner binary and the lib not sharing the same instance of the GC, as explained [here](https://nim-lang.org/docs/nimc.html#dll-generation). And while this can be resolved by linking both binaries against nimrtl.dll, other [crashes do still occur](https://github.com/Serenitor/hotnim) for me, triggered by re/deallocations (e.g. system.del for seqs) and seemingly in relation to how much of the hot loaded code changed.
