Esteban Kuber
Esteban Kuber
Ideally, you would need access to the underlying expression. I think you could optionally pass one in from (likely)`demand_coerce_ty`, which then makes it possible to evaluate the context of the...
Can you add a test file and run `python x.py test src/test/ui --bless`? I want to see how many existing cases would be affected by your change. And after that...
Some information around 2018 edition has been added to https://github.com/rust-lang/reference/blob/master/src/items/use-declarations.md. Is the current state of the documentation enough to close this ticket @petrochenkov?
We now have arbitrary self types in traits. I think whatever syntax we use should approximate or mimic it. Personally, I lean towards the following: ```rust impl Point { pub...
The thing is we already have an appropriate syntax for having a trait with a different receiver than `Self`, which is used for `Pin` in stable already: https://github.com/rust-lang/rust/issues/44874 I believe...
Is there something on the `rustc` side that needs to be done? We could add a new variant with a degree of confidence between `MachineApplicable` and `MaybeIncorrect`. We could have...
CC https://github.com/rust-lang/rust/pull/56220
For traceability, CC https://github.com/rust-lang/wg-async-foundations/issues/19 & https://github.com/rust-lang/rust-clippy/issues/4377
You'll need to re`--bless` :)
r=me after rebasing