Michael Allwright

A couple questions to keep this discussion moving forward: 1. What parts of this RFC are already covered by Parry, what would we have to implement additionally? 2. Is there...

@nilslice there seems to be a couple good solutions proposed above. Would you be open to accepting a PR for either @Dav1dde or @SeokminHong solution? > The team is generally...

This is my complete solution based on the answers above ```rust // asset.rs use once_cell::sync::Lazy; use std::collections::HashMap; use worker::*; use worker::wasm_bindgen::prelude::*; #[wasm_bindgen(module = "__STATIC_CONTENT_MANIFEST")] extern "C" { #[wasm_bindgen(js_name = "default")]...

@SeokminHong not really the place to ask, but what pattern did you use for matching assets in sub-directories? I am finding that `.get_async("/:asset", |_, context| asset::serve(context))` doesn't match on `/images/some_image.png`.

> it's also maybe time to consider dropping `wasm-pack` as the intermediary, and just call `wasm-bindgen` directly. Will investigate. Any news on this front? My two cents would be that...

@RReverser did you find a work around (other than just sticking with `-fexceptions`) for this?

This code here seems sufficient enough to reproduce the problem: ```c++ #include #include __attribute__((import_module("env"), import_name("external_async_function"))) void external_async_function(); int main() { try { throw std::invalid_argument("test"); } catch(const std::invalid_argument& e) { std::cout

Tested the same code with the latest versions (as follows) but I seem to hit the same error. - wasm-opt version: 106 (version_106-10-g22d24fda9) - emcc version: 3.1.8 (3ff7eff373d31d8c0179895165462019221f192e)

Thinking about this a bit more, I suspect that such a feature would require additional functionality from both serde and wasm-bindgen sides to achieve this...

@RReverser do you have any thoughts regarding workarounds that could achieve something like this, i.e., moving a Rust struct containing JsValues to Javascript?