Top rfcs issues

Allow `_ @ CONST` in match arms

Restrict Usage of Shadowing

add a macro `String` to create a new String

Multiple Module Declaration

A-modules A-syntax T-lang

Make alloc-free string manipulation more ergonomic with String::mutate(&mut self, ...)

@estebank I would say discoverability, guessability, and -- maybe the biggest issue to me -- every one-more-thing you have to explain risks being the one thing that blows a newcomer's cognitive budget. Don't get me wrong, overall I've been pleasantly surprised at how quickly my colleagues have gone from zero to productive users of Rust. But there are still so many little surprises in the onboarding experience, that it's easy for a learner to just blow their stack and give up. (I think I'm just basically giving an exegesis for why I'm so excited about all the effort Rust is putting into ergonomics, at least the learning side of it.)

Unimplementable ("Sealed") Traits

A-privacy A-traits T-lang

Variable name aliasing

Proposal: Std: Compile-time reflection.

A-reflection T-lang

Rename type to typedef.

A-syntax T-lang