Derek Schuff

Previous discussion can be found at https://github.com/WebAssembly/design/pull/1064/files#r116468692 and https://github.com/WebAssembly/design/pull/1053#issuecomment-302680149 (and the replies to those)

One sort of fundamental question that hasn't been discussed yet is whether we care about having locations be specific to a function or not; i.e. the byte offset is global...

+cc @sunfishcode Yeah, generally speaking I'm sympathetic to this... for example when this change landed we had to do an update in our CI because the version of node we...

Also it's possible that we may eventually want to enable exception handling by default for C++ (or even for Rust panics?), and that will require reference types.

Yeah, the encoding thing is an interesting problem. Generally speaking I do like the idea of engines expanding the allowable encodings even if a feature itself is disabled. It doesn't...

For more fun variations, check out all the options gcc has for similar properties in C: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html (e.g. const, pure, and reproducible).

While it's true that having assertions on helps sometimes, at least for emscripten-releases I'm not sure it's worthwhile to have Binaryen's configuration be different from LLVM's. It's already the case...

On that note, https://emscripten.org/docs/tools_reference/emsdk.html seems kind of out-of-date with respect to the way most users use emsdk with emscripten-releases (e.g. it still refers to targets like "sdk-upstream-main-64bit" etc. I guess...

Thanks, this is acutally a pass-through to the design repo, so I moved the issue.

@sbc100 you're doing some work on pthread code lately, do you think it might have any impact on this?