Thomas Lively

Update Emscripten support

2

https://github.com/emscripten-core/emscripten/issues/10148 is a report from a cargo-web user whose Emscripten installation is managed by cargo-web but is invalid. I took a look at the cargo-web source, and noticed a few...

Documentation on using Emscripten targets

12

Although most community focus for Web projects is on using the `wasm32-unknown-unknown` target, wasm-bindgen, and wasm-pack to integrate Rust into traditional Web development, the Emscripten targets are still useful for...

Add gc-js-customization as a phase 0 proposal

1

The GC subgroup decided to split the customization of JS accessors and prototypes for GC objects out into a separate proposal.

Updating toolchain requirements in the phases process

9

We briefly discussed this at the 7/7/2020 video meeting and decided to take the discussion to GitHub. Currently the phases process recommends that toolchains implement proposals in phase 3 and...

[feature] Optional and dependent features

8

## Overview Additions to the wasm spec ("features") depend on each other to varying degrees. On one end of this spectrum are features like GC and anyref, for which it...

Now that we no longer have RTTs, every value can be safely stored in a local and we don't need to avoid emitting stacky code that we wouldn't be able...

Emit `i31ref` and `dataref` binary shorthands

1

This depends on V8 having updated its interpretation of these shorthands to be nullable.

Make `i31ref` and `dataref` nullable

2

Match the latest version of the GC spec. This change does not depend on V8 changing its interpretation of the shorthands because we are still temporarily not emitting the binary...

`isConstantExpression` should be combined with `isValidInConstantExpression`

3

These seem like they should do the same thing, but their behavior is very different. Probably that's a bug?

There's no reason an element segment couldn't be filled with arbitrary reference types, but our validator currently only allows function references.