Skip to content

fix: Fix retrieval of AsyncFnOnce::Output #829

New issue

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

Merged
merged 1 commit into from
May 27, 2025

Conversation

ChayimFriedman2
Copy link
Contributor

We shouldn't just assume it's always the second associated type of AsyncFnOnce.

We shouldn't just assume it's always the second associated type of `AsyncFnOnce`.
@compiler-errors
Copy link
Member

I don't see why not but also chalk doesn't seem like it's going to be used by salsa for very much longer... 🤔

@ChayimFriedman2
Copy link
Contributor Author

I don't see why not

Because that could change (in fact it probably did change since this code was written, since now the Output type is the first type in rust-analyzer).

but also chalk doesn't seem like it's going to be used by salsa for very much longer..

Yes, I'm doing that in fear that we might have bugs until then (but I don't know of any).

@compiler-errors
Copy link
Member

whoops typo, *rust-analyzer not salsa

@compiler-errors compiler-errors merged commit 4cf6975 into rust-lang:master May 27, 2025
2 of 5 checks passed
@ChayimFriedman2 ChayimFriedman2 deleted the async-fn-output branch May 27, 2025 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants