Jul 24, 2017 · 1 min read
I hereby request elaboration. :)
It sounds like your main objection is purity? I’m not convinced the interchange format benefit from tracking purity, or that it’s a good default for the high-performance situations WebAssembly is targeting. Let the compiler do any purity tracking you need, so that it can also do the heavy optimization lifting involved in generating easily-JIT-able code.
