So once WebAssembly can call the DOM directly, you would consider Nim's
JavaScript support unnecessary?
The macro facilities of Nim seem very impressive. So maybe ES6 module support
can be done simply as a Nim library, along the lines you describe here? My main
concern here is not to duplicate generated code: If I make two modules in Nim,
A and B, and A imports B, and B imports A, then of course t
I would find support for ES6 modules also very interesting, so that I can use
nim to create ES6 modules, basically letting a nim package correspond to a
module. Treating JavaScript like WebAssembly doesn't make too much sense, in my
opinion: Why not compile just to WebAssembly then, if you are n
