-
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
Make TypeFolder::fold_*
return Result
#85469
Make TypeFolder::fold_*
return Result
#85469
Conversation
This comment has been minimized.
This comment has been minimized.
0119b91
to
f2f2eba
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit f2f2eba77b143e5cdee623c25ecc75b3e2739ecf with merge dd302a4b134912d6af2e70defbb3418a9a4f08a7... |
☀️ Try build successful - checks-actions |
Queued dd302a4b134912d6af2e70defbb3418a9a4f08a7 with parent 3e827cc, future comparison URL. |
f2f2eba
to
e8fcfde
Compare
This comment has been minimized.
This comment has been minimized.
e8fcfde
to
85a1572
Compare
Finished benchmarking try commit (dd302a4b134912d6af2e70defbb3418a9a4f08a7): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
Interestingly, the results are not neutral. There are a few regressions up to 6.9%, but for most tests this looks like a slight improvement up to -2.5%. |
I think overall I'm 👍 on this. I'm not sure perf is something we can "fix"; it's kind of mixed anyways. Either way, we should wait for the FCP on the MCP should finish. |
It is a slight performance hit. I wonder if we can dig a bit more into why -- feels like an opportunity for us to improve our mir optimizations or something. |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit f603ea5bcd5e6ff212609a730f909114de7b2fdd with merge ca44a2dcfa1442a89f4ec1ded3ebef42a4440877... |
☀️ Try build successful - checks-actions |
Queued ca44a2dcfa1442a89f4ec1ded3ebef42a4440877 with parent 6f69192, future comparison URL. |
Finished benchmarking try commit (ca44a2dcfa1442a89f4ec1ded3ebef42a4440877): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
f603ea5
to
9bf9c37
Compare
☔ The latest upstream changes (presumably #85984) made this pull request unmergeable. Please resolve the merge conflicts. |
I'm 👍 on this PR, except for the perf. @LeSeulArtichaut are you still looking into the perf regression here? |
Ping from triage: |
Make `TypeFolder::fold_*` return `Result` Implements rust-lang/compiler-team#432. Initially this is just a rebase of `@LeSeulArtichaut's` work in rust-lang#85469 (abandoned; see rust-lang#85485 (comment)). At that time, it caused a regression in performance that required some further exploration... with this rebased PR bors can hopefully report some perf analysis from which we can investigate further (if the regression is indeed still present). r? `@jackh726` cc `@nikomatsakis`
Introduce `Folder::Error` Equivalent to rust-lang/rust#85469, cc rust-lang/compiler-team#432 rust-lang/types-team#16. This compiles, but there are implementations of `Folder` that still use `Fallible<T>` instead of `Result<T, Self::Error>`. I can make that change if it is deemed beneficial. r? `@jackh726`
Implements rust-lang/compiler-team#432.
This should be easier to review commit by commit.
r? @jackh726 cc @nikomatsakis