Nick Fitzgerald

Use `MaybeUninit` in the return type for `[try_]alloc_layout`

2

`MaybeUninit` wasn't stable when these APIs were added. Now it is. Note that this is a breaking change and will require a version bump.

Consider using the `allocator_api` crate

2

Instead of forking from libstd directly ourselves. This would involve merging `String` upstream into that crate plus any other collections we might end up needing.

Support the WebAssembly object format (Disposition: No)

4

@m4b is this something you would be interested in having in `goblin`?

Despite "title" entry in book.toml, it isn't in <title>

3

I see "Introduction - " as the `` of the book, when I would expect "Introduction - Rust and WebAssembly".

Recently we gained two new helpful tools for debugging memory leaks: * https://github.com/rustwasm/wasm-bindgen/pull/1521 * https://github.com/rustwasm/wasm-tracing-allocator We should add a reference guide for boosting their visibility and explaining how to use...

This section should: * [ ] Explain the current state of unwinding, ie how `panic=abort` is the only option. * [ ] Describe what "aborting" means in this context, and...

This would be a new reference sub-section. Things to mention: * [ ] Dynamically allocated objects owned by JS must be manually freed by JS * [ ] To help...

Waiting on a new wasm-pack release. Right now we tell people to add their username to the end of the package name, but instead we should use scopes and `--access...

By having a single, large allocation instead. The motivation is that the `SmallVec` for each block's outgoing edges' actual argument values was often running out of their inline capacity and...

[meta] Migrate instruction selection to ISLE

29

This is a meta issue to track the migration from hand-written instruction selection and lowering over to using the ISLE DSL. As you port lowering for a clif opcode over...