Lukas Wirth
|
8047512dca
|
Revert "feat: Diagnose some incorrect usages of the question mark operator"
|
2022-10-18 14:18:59 +02:00 |
|
Lukas Wirth
|
381366f1dd
|
Diagnose incorrect usages of the question mark operator
|
2022-10-16 12:58:24 +02:00 |
|
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 |
|
Ryo Yoshida
|
018266a7ff
|
Make ModPath display escaped path
|
2022-08-11 03:41:10 +09:00 |
|
Ryo Yoshida
|
4322cf7f5b
|
Remove EscapedName
|
2022-08-11 01:11:18 +09:00 |
|
Justin Ridgewell
|
5810c8188a
|
Implement IntoFuture type inference
|
2022-08-08 21:05:56 -04:00 |
|
Amos Wenger
|
816f7fe12a
|
Run cargo fix --edition-idioms
|
2022-07-20 15:02:08 +02:00 |
|
Jonas Schievink
|
d2fd137252
|
Use SmallVec to slightly shrink ModPath size
|
2022-07-06 19:49:05 +02:00 |
|
Hongxu Xu
|
f536766efb
|
complete raw identifier with "r#" prefix
|
2022-06-26 14:45:30 +08:00 |
|
Lukas Wirth
|
2642f64570
|
internal: Simplify
|
2022-06-23 20:08:29 +02:00 |
|
Peh
|
1f011fa4a3
|
style: rename crates to kebab case
|
2022-05-01 10:48:58 +00:00 |
|