Eric Holk

Another question we should deal with is whether you can construct Wasm exceptions from JavaScript. I imagine most JS exceptions won't be inspectable to Wasm, but instead fall under a...

Related discussions have cropped up at https://github.com/WebAssembly/exception-handling/pull/49#issuecomment-368889883 and https://github.com/WebAssembly/exception-handling/pull/42#discussion_r167716629. On the one hand, I think the spec should avoid imposing requirements on implementations strategies. On the other hand, I'm not...

Oh sorry, the code snippets I included in my post were in JavaScript, and I left the Wasm code to the reader's imagination. Here's a less imaginary version of the...

`dyn* Debug` and `dyn * Debug` will both parse and compile fine, but I prefer the `dyn*` version.

We've started a [zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/187312-wg-async/topic/.2395985.20-.20Ensure.20.60Context.60.20isnt.20.60Sync.60.2B.60Send.60) on this and also tagged the issue so it will come up in our next triage meeting. We'll report back once we've had the chance...

We discussed this in @rust-lang/wg-async triage today and we all agree that this code should work. We were honestly surprised to find out it doesn't.

Are there particular examples you'd like to see?

Actually, if you have a specific example already in another language, we could try to do a port to Rust. Right now we just use OpenCL C to write the...

Seems reasonable to me. I'm regularly surprised that `Future` isn't in the prelude. A lot of code imports `futures::Future`. Would putting `Future` in the prelude break this code?

Playing devil's advocate for a bit, are `Future` and `IntoFuture` traits that really need to be in the prelude? Most people don't implement `Future` directly, and probably even fewer call...