Tracking upstream Rust feature stability and RFCs that affect wasm

[fitzgen]

Awaiting Stability / Implementation

• Allocator traits and std::heap

• Tracking issue for changing the global, default allocator (RFC 1974)

• feature(proc_macro) (used heavily by wasm-bindgen)

• Custom test frameworks

RFCs

• eRFC: Custom test frameworks The eRFC was merged, and this is now awaiting implementation and then stabilization.

• RFC: Introduce panic_thin, a fmtless alternative to panic_fmt

Unstable and Need RFC

• Intrinsics for growing and insecting wasm memory

Completely Unimplemented and Need RFC

• Cargo templates

Bugs

• LTO ignored for all crate types if any crate type doesn't support it This means that LTO is disabled if you enable rlibs and cdylibs for both native testing/benching and building for wasm.

---

Please add links to other RFCs and feature stabilization issues that are relevant and help us keep them up to date!

[mgattozzi]

Do we want to open an issue for upstream non rust ones like llvm or the webassembly group itself?

[fitzgen]

Do we want to open an issue for upstream non rust ones like llvm or the webassembly group itself?

For sure!

[fitzgen]

Does anyone know the latest cargo template (pre) RFC? Would like to add it here.

[mgattozzi]

Maybe someone on the cargo team would know. Maybe @matklad or @alexcrichton? The only template pre-rfc I found is the old one on internals.

[matklad]

@mgattozzi there's no any active RFC about templates currently, the discussion died out :(

[mgattozzi]

@matklad that's unfortunate. cargo does everything I need, but this is the one feature I still want.

[fitzgen]

I added a new "completely unimplemented and need rfc" section for the templates ;)

[alexcrichton]

I think that this has sat around long enough that we've solved enough and otherwise this isn't tracking too too much any more so I'm going to close it.