Agree with Araq here; find a way to do it with (a possibly improved) staticExec - or alternatively, it could be solved with a bidirectional communication channel through pipes (or sockets or shared memory, though these aren't good ideas either) if Nim code with access to compiler types etc. needs to interact with external code.
But invading the compiler's memory address space is a recipe for disaster. At first it will work, but down the line people will complain that the nim compiler is buggy and unstable, but it will later turn out that the crash is caused because of a memory corruption caused by importing a library 3-layers deep which uses the compile time FFI. But seriously, I think even staticExec+staticRead is more than enough. At some point, you have to rely on a build/make tool that can do more than your language do internally.
