-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
support higher-ranked regions in opaque type inference #100503
Conversation
r? @wesleywiser (rust-highfive has picked a reviewer for you, use r? to override) |
r? @ghost |
6d8101f
to
00ad09a
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 00ad09a6d887bb405b066fcb3cfd7862016544af with merge 3d24f8fa902ae9abd51f0d08aa8a0d7b2895840f... |
☀️ Try build successful - checks-actions |
Queued 3d24f8fa902ae9abd51f0d08aa8a0d7b2895840f with parent 6ce7609, future comparison URL. |
Finished benchmarking commit (3d24f8fa902ae9abd51f0d08aa8a0d7b2895840f): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
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 may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
When checking `'sup: 'sub`, take placeholder elements into account. This wasn't a problem previously (I hope!) because `eval_outlives` was only used for type_tests, which don't have higher-ranked outlive relations.
00ad09a
to
e6b62a0
Compare
Should be ready now. I've done a couple perf changes that might help. r? types |
☔ The latest upstream changes (presumably #100847) made this pull request unmergeable. Please resolve the merge conflicts. |
r? types |
Nominating to get this moving again (though I imagine this will get delayed until after holidays) |
unnominating with the expectation that @aliemjay will either schedule a meeting with niko or assign this PR to me. |
Hello @aliemjay! Noticed there's some merge conflicts, what's the status of this PR? |
given the time i've spent on this topic recently r? @lcnr we probably want to wait on the t-types meeting about opaque types today though before making progress on this |
Blocked on #113575 |
don't ICE on higher ranked hidden types This shouldn't allow more code to compile, only replaces the ICE with a nicer error message. Fixes rust-lang#97098. Fixes rust-lang#97099. Fixes rust-lang#108399 Fixes rust-lang#104196 Fixes rust-lang#113481 Fixes rust-lang#103186 Fixes rust-lang#100818 r? `@lcnr` (because you showed interest in rust-lang#100503 :)
No longer blocked as the pr it was blocked on, is merged |
@aliemjay any updates on this? |
…r=lcnr test that we do not support higher-ranked regions in opaque type inference We already do all the right checks in `check_opaque_type_parameter_valid`, and we have done so since at least 2 years. I collected the tests from rust-lang#116935 and rust-lang#100503 and added some more cc rust-lang#96146 r? `@lcnr`
…r=lcnr test that we do not support higher-ranked regions in opaque type inference We already do all the right checks in `check_opaque_type_parameter_valid`, and we have done so since at least 2 years. I collected the tests from rust-lang#116935 and rust-lang#100503 and added some more cc rust-lang#96146 r? `@lcnr`
Rollup merge of rust-lang#121386 - oli-obk:no_higher_ranked_opaques, r=lcnr test that we do not support higher-ranked regions in opaque type inference We already do all the right checks in `check_opaque_type_parameter_valid`, and we have done so since at least 2 years. I collected the tests from rust-lang#116935 and rust-lang#100503 and added some more cc rust-lang#96146 r? `@lcnr`
Closing this as inactive. Feel free to reöpen this pr or create a new pr if you get the time to work on this. Thanks |
Best reviewed commit by commit.
Cc @WaffleLapkin this may help #93582.
Fixes #96146.
Fixes #97098.
Fixes #97099.
Builds on #100375.