wasm: slice copy bombing out about tinygo

[trashhalo]

wow fast turn around! oh yea my actual code isnt returning a string I just tried to hack it up to make sense in isolation.

thanks so much for your work on this project!

[aykevl]

Yes, that looks like a bug. Thank you for the report! Currently investigating.

However, note that you can't currently return a string from WebAssembly. This is a limitation of WebAssembly at the moment. In my experiments, it doesn't return anything at the moment, probably because it stores a pointer to the result somewhere but I don't know where exactly. Also, it appears to skip the first parameter for some reason.

[aykevl]

It was an incorrect backwards copy of a zero-length slice: even while being zero length, it tried to copy one byte. The bug should be fixed now.

I still don't understand why the first parameter from JS is skipped. It looks like it happens during WebAssembly codegen (after all optimization passes etc. have run) because the function signature in the IR is correct: two i32 parameters.

You can test that the function works by printing the resulting string to the console:

    println(page)