Hacker News Reader

I am so afraid that WebAssembly will make too many assumptions that will prevent Go from targeting it as a platform.

A well designed assembly language should be targetable by any well designed IR. When the Go team decided to work on their own compilers instead of writing frontends for existing compilers, they chose to take on that effort.

What assumptions is wasm making that will prevent Go from targeting it, and why are those assumptions fundamentally harder for Go to target than LLVM IR?

Not sure about assumptions made by wasm, but current limitations preventing Go from targeting it are:

> there is no efficient way to implement setjmp/longjmp functionality currently, therefore it's not a viable target of a gc port. We need to wait until it gets real stack unwinding and exception handling support.

https://github.com/golang/go/issues/18892

Well, thankfully TFA includes a short paragraph talking about the standardisation of exception handling, so here's hoping to have that resolved soon.

Reply on news.ycombinator.com