-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Lazy TAIT preparation cleanups #89024
Lazy TAIT preparation cleanups #89024
Conversation
@@ -584,50 +602,8 @@ fn find_opaque_ty_constraints(tcx: TyCtxt<'_>, def_id: LocalDefId) -> Ty<'_> { | |||
// FIXME(oli-obk): trace the actual span from inference to improve errors. | |||
let span = self.tcx.def_span(def_id); | |||
|
|||
// HACK(eddyb) this check shouldn't be needed, as `wfcheck` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the mir_borrowck
call above will invoke the checking logic, duplicating it here with delay_span_bug adds no additional safety net
(lgtm) |
@bors r=nikomatsakis |
📌 Commit fed385b38b69f879cdade3de43b72b16df63cb29 has been approved by |
@bors r- |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit fed385b38b69f879cdade3de43b72b16df63cb29 with merge be8d9ae4358f73fdda58b9349a86260cfa25c94e... |
☀️ Try build successful - checks-actions |
Queued be8d9ae4358f73fdda58b9349a86260cfa25c94e with parent db1fb85, future comparison URL. |
Finished benchmarking commit (be8d9ae4358f73fdda58b9349a86260cfa25c94e): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf. @bors rollup=never |
@bors r=nikomatsakis |
📌 Commit fed385b38b69f879cdade3de43b72b16df63cb29 has been approved by |
⌛ Testing commit fed385b38b69f879cdade3de43b72b16df63cb29 with merge 833b4b869a15d7f533a04954f4b79a698d6878b7... |
💥 Test timed out |
This comment has been minimized.
This comment has been minimized.
@bors retry |
⌛ Testing commit fed385b38b69f879cdade3de43b72b16df63cb29 with merge 71dc5a38fe6b245c7acb00b6eb73e0a9af08a076... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
…f-check, as wf-check can by definition only check TAIT in return position and not account for TAITs defined in the body of the function
fed385b
to
6067ead
Compare
@bors r=nikomatsakis |
📌 Commit 6067ead has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (2b862be): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
this was previously used for opaque types but became unnecessary after rust-lang#89024
Check that TAIT generics are fully generic in mir typeck instead of wf-check, as wf-check can by definition only check TAIT in return position and not account for TAITs defined in the body of the function
r? @spastorino @nikomatsakis