Niko Matsakis
Niko Matsakis
@rfcbot fcp merge We discussed this RFC in the lang-team design meeting. There was general excitement about the contents (subject to one minor caveat which I will file as a...
@rfcbot concern leaving-us-in-an-inconsitent-state The RFC as proposed leaves us in a bit of inconsistent state. It means that you can write ```rust let [mut x] = &mut [22]; ``` ...and...
Add `covering set` impl for generic version of trait when all values of a const are covered by impls
@JulianKnodt sorry I've let this sit so long! I can review it if you want to rebase, but I'd like to know a bit of context first. Is this something...
I agree with 1 and 2. I don't 3 follows just from those 2. I do however agree with it... specifically the current situation is misleading for people and can...
@rfcbot reviewed This seems like a logical extension, I can't really see any reason *not* to do this.
@clarfonthey the interaction with exhaustiveness is interesting, can you elaborate-- are there surprising cases where the exhaustiveness check results are not what users would probably expect?
Closing in favor of #3347
I'm a big fan of this proposal. Using synchronous I/O from inside async functions is a common footman. It's worth noting that the same attribute would be useful to rayon...
@RalfJung we had some discussion in the spec about this wording. I'm having a hard time (quite honestly) knowing with precision what you are saying and what the spec is...
Oh, I like this. Cute idea.