This is for the development process, aiming to obtain an interactive experience. This would not be there for production. I may want to do something similar with a plugin system, if that's possible, though I'm not planning to implement that.
At the moment the only way I can see how to do the above is to force compilation to C files, parse the JSON produced by the compiler and compile the files manually to a dll/dylib with a custom build script. I haven't done this, as it's quite a bit of effort, so I am not sure if this works. I have been exploring the compiler a bit more and trying to understand how the standard library is compiled to a dll, which it seems there is one file importing all the standard library modules. Question: if I dedicate one nim file to the imports of my dependencies (e.g. other nim modules or some modules compiling C files such as sokol), is it possible to compile this module to a dll and then use this dll for the imports it references to in other parts of my program? If so - how do I do this?
