-
Notifications
You must be signed in to change notification settings - Fork 13.6k
don't assume we can *always* find a return type hint in async fn #65235
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
don't assume we can *always* find a return type hint in async fn #65235
Conversation
0f16d25
to
f7d0a8e
Compare
@bors r+ |
📌 Commit f7d0a8e has been approved by |
@bors p=1 -- ICE/regression in async-await |
…eturn-ice, r=cramertj don't assume we can *always* find a return type hint in async fn In particular, we sometimes cannot if there is an earlier error. Fixes rust-lang#65159 r? @cramertj, who reviewed the original PR
⌛ Testing commit 5a24534 with merge 88624206022c8627d731d4dc9725d6c384e8c02a... |
💔 Test failed - checks-azure |
I can't really tell what happened with this build -- did something go wrong? All I see is "cancelled by @alexcrichton" |
@bors r- @nikomatsakis "cancelled by alex" is just the other builders being killed because another one failed. Azure Pipelines requires using a personal token when cancelling a build and it just so happens it's Alex's one. Seems like the i686-gnu builder is what caused the failure though. Build log |
@pietroalbini thanks. I .. don't really have any idea how this PR caused that error, though. Huh. |
is this "RUSTC-TIMING" stuff normal, or does that indicate some special mode? (cc @pietroalbini) |
Yeah, it's normal. On CI rustbuild is configured to emit detailed timings for each step so infra can analyze slowdowns more easily. |
In particular, we sometimes cannot if there is an earlier error.
f7d0a8e
to
48fff6f
Compare
ok I rebased and ran my local tests. Due to #63520 x.py test didn't run to completion, but I'll delete that test locally and try again. Weird that the bot above seemed to die building libstd. |
📌 Commit 48fff6f has been approved by |
⌛ Testing commit 48fff6f with merge a0192c324d7eeda991ed8dc8197f16ac683df59a... |
…eturn-ice, r=cramertj don't assume we can *always* find a return type hint in async fn In particular, we sometimes cannot if there is an earlier error. Fixes rust-lang#65159 r? @cramertj, who reviewed the original PR
@bors retry rolled up. :) |
⌛ Testing commit 48fff6f with merge e43da6e749cfc2153a906d2b956e2e77801f515d... |
…eturn-ice, r=cramertj don't assume we can *always* find a return type hint in async fn In particular, we sometimes cannot if there is an earlier error. Fixes rust-lang#65159 r? @cramertj, who reviewed the original PR
@bors retry rolled up. :) |
⌛ Testing commit 48fff6f with merge 70c5542f0d41f1dc75cc56e0d9a1b01c00e736e6... |
…eturn-ice, r=cramertj don't assume we can *always* find a return type hint in async fn In particular, we sometimes cannot if there is an earlier error. Fixes rust-lang#65159 r? @cramertj, who reviewed the original PR
@bors retry rolled up |
Rollup of 14 pull requests Successful merges: - #64603 (Reducing spurious unused lifetime warnings.) - #64623 (Remove last uses of gensyms) - #65235 (don't assume we can *always* find a return type hint in async fn) - #65242 (Fix suggestion to constrain trait for method to be found) - #65265 (Cleanup librustc mir err codes) - #65293 (Optimize `try_expand_impl_trait_type`) - #65307 (Try fix incorrect "explicit lifetime name needed") - #65308 (Add long error explanation for E0574) - #65353 (save-analysis: Don't ICE when resolving qualified type paths in struct members) - #65389 (Return `false` from `needs_drop` for all zero-sized arrays.) - #65402 (Add troubleshooting section to PGO chapter in rustc book.) - #65425 (Optimize `BitIter`) - #65438 (Organize `never_type` tests) - #65444 (Implement AsRef<[T]> for List<T>) Failed merges: - #65390 (Add long error explanation for E0576) r? @ghost
Nominating as fix for #65500. |
@estebank backport was declined for the PR this depends on (#64999 (comment)). |
@Centril ack. Please remove the label, on mobile right now. |
In particular, we sometimes cannot if there is an earlier error.
Fixes #65159
r? @cramertj, who reviewed the original PR