diff options
| author | bors <bors@rust-lang.org> | 2024-07-29 12:55:53 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-07-29 12:55:53 +0000 |
| commit | 51130d8222c3228a9576e3e114a0016510a9da0f (patch) | |
| tree | 61ae3f07c15ec9a783b20b0162fa589b5648e9cc /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp | |
| parent | ca16c0633d438ef037f3b20c3616691df51f0fd0 (diff) | |
| parent | 825034566ad5e752cb6d422ab5f38a5aaff08bb7 (diff) | |
| download | rust-51130d8222c3228a9576e3e114a0016510a9da0f.tar.gz rust-51130d8222c3228a9576e3e114a0016510a9da0f.zip | |
Auto merge of #17736 - hyf0:hyf_09234908234, r=Veykril
feat(ide-completion): explictly show `async` keyword on `impl trait` methods
OLD:
<img width="676" alt="image" src="https://github.com/user-attachments/assets/f6fa626f-6b6d-4c22-af27-b0755e7a6bf8">
Now:
<img width="684" alt="image" src="https://github.com/user-attachments/assets/efbaac0e-c805-4dd2-859d-3e44b2886dbb">
---
This is an preparation for https://github.com/rust-lang/rust-analyzer/issues/17719.
```rust
use std::future::Future;
trait DesugaredAsyncTrait {
fn foo(&self) -> impl Future<Output = usize> + Send;
fn bar(&self) -> impl Future<Output = usize> + Send;
}
struct Foo;
impl DesugaredAsyncTrait for Foo {
fn foo(&self) -> impl Future<Output = usize> + Send {
async { 1 }
}
//
async fn bar(&self) -> usize {
1
}
}
fn main() {
let fut = Foo.bar();
fn _assert_send<T: Send>(_: T) {}
_assert_send(fut);
}
```
If we don't distinguish `async` or not. It would be confusing to generate sugared version `async fn foo ....` and original form `fn foo` for `async fn in trait` that is defined in desugar form.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
