Josh Goebel

> What if it is overwritten by the same value? VERY, VERY unlikely, you'd use a sequence of bytes... 8 or 16 should be safe enough and make this as...

> Move memory map to the end of the memory Please explain exactly what you are moving when you say "memory map"... do you mean the entire documented registers and...

IMHO: This is simply something our "hardware" doesn't allow because of our hard-wired RAM layout. I personally don't think we should change WASM-4 overall (or add complexity) to accommodate _a...

> It may even enter a loop eternity. How? > WARNING: this bug is relevant for every language! True, but the _fix is currently only relevant for Rust_ as I...

> True, but the fix is currently only relevant for Rust as I understand it - correct me if I'm mistaken. ? Ok, so it seems the idea is that...

> Something could override a return pointer. The actual function call stack is in the WASM VM, not the memory... no? Though I suppose technically with indirect calls this might...

I'm not entirely unfamiliar... but the reason WASM has opcodes like `local.get` is to retrieve things from the WASM [outside] stack (I presume locals are on a stack or stack...

This happens automatically at compile time if someone has `wasm-opt` installed... is it too much to expect someone to modify their build settings if they wanted to add an extra...

Could it be "both" is perhaps an option...? ...if it's much easier to package the `nodejs` version then perhaps it could be used and users just deal with how slow...

Feels like we need a `note` API... the higher-level libs I'm writing for TIC-80 have a note API for playing notes that does the translations from notes into frequencies and...