WebAssembly Interpreter Engine
vimirage opened this issue · comments
There's no one on the team who's actually going to focus on the WebAssembly engine.
I'm demotivated.
Skye is unable to commit to this, whatever the reason is.
I recommend merging the JavaScript and WebAssembly into the same code. Not separate compilation paths and such, just a Wasm parser that feeds into creating JS functions using 'Wasm' opcodes in the stack machine, that are part of the same enum as JS is.
This should be easy, and get it functional quickly.
Thoughts?
if we go for a interpreter for wasm for now then I highly recommend waiting on me to finish https://github.com/mierenmanz/interretialem.
Soon it will be published and will partially be usable for nova
@MierenManz it's an empty repository.
Pulling in an external crate forces code separation.
we don't need to pull it in externally. I'm fine with intergrating the core into nova and them rewriting interretialem to use nova's wasm core. For now that will be a empty repository due to it being for school. Once it is no longer a school project I will share it more openly
I'd still rather get something into Nova much sooner.
End of Dec and it should be ready