Ryan Hunt

Okay, coming back to this after discussing this with several folks offline. I didn't fully understand the issue because I thought the issue was with how to specify certain wasm...

> > 1. Add an option to the WebAssembly JS-API compilation endpoints (module constructor, compile, compileStreaming, etc): > > > > ``` > > dictionary WebAssemblyCompileOptions { > > optional...

IIRC, the difficulty here is circular dependencies among header files. Maybe when we break modules into multiple header files, we could move all forward declarations needed to a central header?...

I don't see this in this PR or the overview, but is it intended for `exn` to be passable to/from JS through params/results, or be like `v128` and cause TypeError's?

Okay, that was my understanding as well, but wanted to make sure. SpiderMonkey throws a TypeError in ToJSValue.

> My understanding is that this would not but much work from the implementation side. @backes and @eqrion perhaps you could confirm? > > (To be clear this would _not_...

So just to make sure I understand what's being proposed, this would be a general '(table i64)' feature even if we maintain a

> I do see that Firefox is throwing a TypeError and Chrome is throwing a RuntimeError. @eqrion would it be possible to change SpiderMonkey's behaviour to a RuntimeError? This would...

This is because the support for #[cfg] is under documented and not complete. There are two limitations you're running into here, 1. You need to provide a mapping from rust...

Yes that's about correct. We generate one header for all configurations, using C's preprocessor to switch between declarations.