kennytm

this is like one of the capturing alternatives proposed in https://github.com/rust-lang/rfcs/pull/3680#issuecomment-2308559508. as explained in https://github.com/rust-lang/rfcs/pull/3680#issuecomment-2328377258 it is very hard to grasp the scope/lifetime of the `cc {}`'ed expression for newcomers.

since #18473 has changed the toolchain to `nightly-2025-02-28` I think this PR is no longer necessary.

@tmccombs this has the same issue as applying Projectable on `Cow`, which is that `Option` is a *container* of `T` rather than a *pointer* to `T`, meaning accessing its field...

@Nadrieril #3717, not yet merged, mainly because inline discussion has crap UX. This is off-topic, let continue over there if you like to. (Also if someone started a discussion in...

I don't understand the motivating example. As there is not an `E: Default` bound, what does `(None::)?` even mean.

Split off from https://github.com/pingcap/tidb/issues/43007#issuecomment-2373481127. Since that the table schema's crc64xor is just the sum of the table's data files, the schema checksum is redundant. BR restore could simply rely on...

is this supposed to be read together with #3628?

i think this will cause some longer-than-expected sequences before disambiguation can be resolved: ```rust fn g() where T: for ``` the `for` here may be the looping expression or the...

@joshtriplett > In this case, the parser *should* know that it's expecting a type rather than a function body, right? No, `T:` is a perfectly fine WhereClauseItem (it just asserts...

yeah I know the inner attribute is bad style but will the following apply the attribute to the function item itself? ```rust fn X() unsafe { #![allow(non_snake_case)] } ``` and...