Crystal Durham

There have been discussions about supporting running proc macros in wasm natively. Offering precompiled wasm binaries is technically a separate problem from supporting a wasm proc_macro bridge. For the wasm...

There's two asks you're making: - Native support for running proc macros in wasm. Higher level FFI has *absolutely no* impact on this; the RPC between the proc macro server...

To be explicit: running proc macros on wasm has been discussed, but *that's the extent* of what's been practically discussed. Nothing about publishing wasm blobs to cratesio; solely just compiling...

Alright, yes, especially because it's just a set of flags that I need to pass through to the macro, I've successfully set up to pass some magic keywords at the...

I also think it would be reasonable to prohibit identically matching rules in a single `Or` disjunction.

FWIW I think let chains and let-else are going to be contentious formatting-wise no matter what choice is taken. This is basically guaranteed to be a "nobody's favorite" kind of...

> > This is basically guaranteed to be a "nobody's favorite" kind of choice. > > This made me laugh out loud, both because I think it's 100% correct but...

#2497 is relevant w.r.t. `miri_error`. By discussion in that issue (Miri is for catching language UB, not library UB; run natively compiled code with debug/careful assertions to catch library UB),...

Using `MaybeUninit` instead of `u8` for the buffer is desirable to keep the optimization path (mostly) "zero cost" even for `dyn Display` by avoiding redundant zeroing of the stack memory[^3]....

> why in the standard library Primarily, for coherence reasons. Because the traits are marked `#[fundamental]`, coherence knows that types *don't* implement the trait, and this works today. Ideally, we...