Spxg

> directly avoiding the need for a Rust slab entirely and hence Rust allocations entirely. But in this case, there will happen as long as `memory.grow`: ```rust #[cfg(test)] mod tests...

You mean to use readonly on the struct, and then only generate getters for all the public fields, right? That sounds reasonable.

I'm unfamiliar with nix, what do I need to do?

@seanmonstar Hi, Is it possible to merge it even if it is not compatible with non-chromium browsers?

> is an acceptable breaking change Probably not, especially considering the widely use of crates such as `ring` and `zstd-sys` that require compiled C code. > In this case, the...

> They have to match up LLVM versions, basically. You can look up with LLVM version is used by which Rust version and match up the Clang version. Well, `rustc...

> This commit, [#4642](https://github.com/wasm-bindgen/wasm-bindgen/pull/4642), changes the externref symbol to only exists when the `reference-types` target-feature is enabled. I found another issue: under Rust 1.82, `cfg!(target_features = "reference-types")` is false, but...

> until we have a replacement in place This replacement needs to be maintained by us or someone can guarantee long-term maintenance? Considering the functionality and popularity of `wasm-pack`, perhaps...

Could you provide a more detailed backtrace? Also, are you using a locally built version of wasm-bindgen?

Do not run a second round, as ownership has been transferred. Here are some details: https://github.com/wasm-bindgen/wasm-bindgen/issues/4289#issuecomment-3476572211 ```ts test('array_ownership', () => { const struct1 = create_my_struct(10); const struct2 = create_my_struct(20); const...