Thomas Lively

@lukewagner I'll be interested to hear about why it is useful to draw a distinction between `adapter_module` and `component`, but I'm happy to defer further discussion until we have a...

I am interested in the LLVM support problem, but I'm not familiar with the .NET ecosystem. Does .NET currently use LLVM, or is the question of LLVM support only coming...

Right, but I'm wondering how LLVM relates to the .NET ecosystem. It's actually possible that we will not end up implementing GC or other features in LLVM if for instance...

FWIW, @pmatos and @asb are working on adding support for reference types (eventually including GC types) to LLVM and even clang, so it is likely that LLVM-based languages and languages...

Perhaps I'm biased toward having lots of instructions by working on SIMD, but I think the simplest and most composable solution would be to create throwing versions of all the...

I guess for now the options are to trampoline through JS before executing trapping operations to convert traps into exceptions or to guard against trapping operations explicitly in the Wasm....

Adding new throwing instructions seems clearly simpler than adding hooks or new control flow constructs because it does not introduce anything fundamentally new to the spec and does not raise...

Oh right, I hadn't thought about all the user-space setup a runtime would have to do before actually throwing an exception. That being said, throwing instructions still seems like the...

Yes, WebAssembly has so far (almost) avoided having module-level configuration bits and hooks like that to keep modules composable and decomposable. Whether the module-level configuration were a bit or a...

It seems like this simplest and least intrusive change would be to split `externref` off of the type hierarchy. Applications that need to use subtyping and casting could just use...