Niko Matsakis

I seem to have made this worse!! Related PRs #228 and #230

The Rust foundation’s purpose is to enable Rust maintainers to do their best work happily. The Rust core team believes that the best Rust will be made by happy maintainers,...

@matklad > Will the foundation fund each and every developer working on rust lang? probably not I've posted an answer to this part of your question in #13.

> trait definitions currently assume Self is ?Sized + MetaSized (kinda? they allow functions that require Sized too which is odd), if this proposal means that in order to use...

One further thought: the whole `const _: () = { .. }` thing was a total hack -- albeit, a useful one. I do wonder if it's time to add...

I would prefer to simply deprecate it across all editions and leave possible 2027 removal as something to be decided on the next edition. This fits with our general strategy,...

@rfcbot reviewed I am generally aligned with @tmandry here, and I concur with @wesleywiser that we should try not to make monomorphization behavior hard-coded. I'm signalling as reviewed because I...

Re-reading, I see @joshtriplett wrote... > (Both for simplicity and because I think projects will want an abbreviated version badly enough that they'll end up defining it as a macro...

@rustbot labels +I-lang-nominated I'm nominated to take the temperature of the @rust-lang/lang team on this RFC -- I'd like to see it move forward! I'm going to give it a...

Gave this a quick read. One thing I would note is that I think that the RFC should highlight more that it also enables `*const self` methods -- this is...