We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
async fn
using TAIT (type alias implement trait) in async function leads to a stack overflow. This is not the case for sync functions.
TAIT
rust-analyzer version: rust-analyzer 1.80.0-nightly (faefc618 2024-05-07)
rustc version: rustc 1.80.0-nightly (faefc618c 2024-05-07)
editor or extension: using zed, but verified in the CLI
relevant settings: N/A
repository link: https://github.com/indietyp/rust-analyzer-regressions/tree/async-tait
code snippet to reproduce:
#![feature(type_alias_impl_trait)] type Foo = impl std::fmt::Debug; async fn foo() -> Foo { 42 }
You can test this yourself using:
$ git clone git@github.com:indietyp/rust-analyzer-regressions.git && cd rust-analyzer-regressions && git switch async-tait $ rustup run nightly-2024-05-08 rust-analyzer --version $ rustup run nightly-2024-05-08 rust-analyzer analysis-stats .
the output of the commands has been posted in the README.md of the repository.
The text was updated successfully, but these errors were encountered:
@rustbot claim
Sorry, something went wrong.
Kohei316
No branches or pull requests
using
TAIT
(type alias implement trait) in async function leads to a stack overflow. This is not the case for sync functions.rust-analyzer version: rust-analyzer 1.80.0-nightly (faefc618 2024-05-07)
rustc version: rustc 1.80.0-nightly (faefc618c 2024-05-07)
editor or extension: using zed, but verified in the CLI
relevant settings: N/A
repository link: https://github.com/indietyp/rust-analyzer-regressions/tree/async-tait
code snippet to reproduce:
You can test this yourself using:
the output of the commands has been posted in the README.md of the repository.
The text was updated successfully, but these errors were encountered: