Nick Fitzgerald

Initial strawperson proposal for debugging modules

10

Disclaimer: This is very much a work-in-progress and nothing I've written up is set stone! My hope is that we can merge this PR and continue design in the form...

The coredump spec currently doesn't mention tables, presumably because it isn't clear how to encode reference values in core dumps. But this is still an issue today even without tables...

Coredumps: Allow truncating locals and operand stack vecs when all values are optimized away

2

In Wasmtime, we don't currently include locals or the operand stack in core dumps currently (although we intend to soon) and in fact have even lost all information about how...

Coredumps: how to represent process/posix-y info like executable name, arguments, and environment

4

Wasm itself doesn't have these concepts. The closest thing it has to a process is the [store](https://webassembly.github.io/spec/core/exec/runtime.html?highlight=store#store). This impedance mismatch is visible when looking at a collection of Wasm instances...

Type constructors should have a `wasm_engine_t*` parameter

10

In general, runtimes will deduplicate and canonicalize function types so that a signature can have a single engine-wide ID that can be used when type checking indirect calls across modules...

The reference types proposal removed `anyref` and replaced it with `externref`.

Add `watch` and `serve` subcommands to `wasm-pack`

17

[**Rendered**](https://github.com/fitzgen/rfcs-1/blob/wasm-pack-watch-and-serve/text/010-wasm-pack-watch-and-serve.md) ---------------------------- cc @ashleygwilliams @alexcrichton @DebugSteven @drager

Add an amendment to the RFC process

13

[Rendered](https://github.com/fitzgen/rfcs-1/blob/rfc-process-amendment/text/009-rfc-process-addendum.md)

Validation

4

Should be able to take an AST and some extra wasm typing context (probably expressed as a trait) and validate that the bindings described by the AST are well-formed.