Kevin Reid

I look forward to being able to write fewer `as` casts, and this seems like a well-defined chunk of them to carve off. Thoughts: * The RFC does not discuss...

> But overall it's not obvious to me in which contexts you'd want to require a truncation, Here’s one I can think of: If you have an integer that’s uniformly...

I hadn't even thought of different namespaces, but that's a good point — even without any `use ... as`, a library author could **accidentally reexport** a prelude item sharing the...

@hellow554 Yes, that is exactly what would be flagged by this lint. It is a tradeoff between different features the code could have, just like many other clippy lints —...

As the author of this proposal, one of the things I would like it to be good for helping people avoid confusion, or writing confusing code, by _unintentionally_ shadowing a...

Commit 9c2b258a10c99082990a47f66c958ce76d7f7bb5 adds the core implementation of reprojection, but it needs significant further work so it is not yet enabled. I also came to realize while working on it that...

Current status of work on this: * I have an unmerged implementation of gap-filling. However, it has very visible flaws: * Pixels from the UI spread and contaminate the view...

"mention" has the disadvantage that the intended default user-visible effect of `#[mention(x)]` is to *not* mention it when building. This is at odds with the verb interpretation of `#[warn(x)]` and...

> The current doc says "The toolchain is chosen in the order listed above..." so I'd expect `rustup override` to take precedence over `rust-toolchain.toml` (so indeed the targets and components...

A further idea: the `SizeHint` type could distinguish “this type or one of its parts did not produce a size hint” from “this type has no upper size limit”. This...