bors 1da9156b0d Auto merge of #12982 - jridgewell:into_future, r=Veykril
Implement IntoFuture type inference

One of my projects is using [IntoFuture](https://doc.rust-lang.org/std/future/trait.IntoFuture.html) to make our async code a little less verbose. However, rust-analyzer can't infer the output type of an await expression if the value uses `IntoFuture` to convert into another type. So we're getting `{unknown}` types everywhere since switching.

`foo.await` itself [desugars](e4417cf020/compiler/rustc_ast_lowering/src/expr.rs (L644-L658)) into a `match into_future(foo) {}`, with every `Future` impl getting a [default](e4417cf020/library/core/src/future/into_future.rs (L131-L139)) `IntoFuture` implementation. I'm not sure if we want to disable the old `future_trait` paths, since this only recently [stabilize](https://github.com/rust-lang/rust/pull/98718).
2022-08-18 07:37:47 +00:00
..
2022-07-20 15:02:08 +02:00
2022-08-17 21:44:58 +08:00
2022-08-17 21:44:58 +08:00
2022-08-17 21:44:58 +08:00
2022-08-01 13:47:09 +02:00
2022-07-31 19:27:20 +02:00
2022-08-17 21:44:58 +08:00
2022-07-20 15:02:08 +02:00
2022-08-17 21:44:58 +08:00
2022-08-17 21:44:58 +08:00
2022-08-06 17:25:02 +03:00
2022-08-17 21:44:58 +08:00
2022-07-20 15:02:08 +02:00
2022-08-17 21:44:58 +08:00