@filippo what kinds of settings preclude forking?

@swatters right now i am personally fine with using the lack of goto support as an excuse not to dabble in wasm yet because i have other priorities

@swatters sandboxed code is possible and cool. if posts like this from andy wingo weren't describing wasm as a force for exclusion and if there were much better tooling for integrating wasm across languages (not having to use webpack for rust for example) i would be a lot more interested in it as an ecosystem

@swatters addressing this is not a matter of advertising what it's good for or what's interesting about it. there are a lot of interesting technologies and wasm is not the only sandbox layer. it would be interesting if it was interested in being a cross-language compile target. its continued disinterest in supporting arbitrary CFGs directly because v8 doesn't want to really pokes a hole in the argument that it's supposed to be about more than the v8/browser/chrome environment

@swatters i am not looking for documentation about it i'm building c++-rust bridges in wasm and the c abi and the fact that the tooling for this does not already exist is a really huge problem and indicative that in fact a lot of people are not using wasm as a useful translation layer between languages but as an exotic compile target in which toolchain support is being used to preclude linguistic interop

@swatters i am fully aware of what wasm is and is good for. i am critiquing andy wingo's portrayal of it here (significant since he is a very clouty implementor) and in general i'm concerned about how people want to (mis)use it to play political games to enclose instead of expand

@dalias thanks i might be using this