WebAssembly in 2018.2 vs 2017.4

[Marco-Trivellato]

@bigbrainz

Is the WebAssembly in 2018.2 better/different than what’s in the latest 2017.4 release? Or were they able to push any of those adjustments backwards in to 2017.4? It makes me nervous to switch to 2018 right now because of where we are in our release cycle, but I’m curious if we’re missing significant advantages and improvements using WA in 2017.4 like we are now.

If there are differences or benefits, could you please describe them just a bit?

For example, I imagine I wouldn’t get the automatic memory expansion or maybe multi-threading? But in terms of general stability and functionality they seem to be performing the same in my tests.

Currently my test of 2017 WASM is actually more stable than the 2018.2 version, which generates a “RuntimeError: memory access out of bounds” as I play through.

Many thanks!

related discussion happening here .

If you are happy with 2017 and you don’t want to risk upgrading, then you should stick with it