Skip to content
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

Forgone caching in cycles caused much overflow in trait solving #61960

Open
1 of 4 tasks
pnkfelix opened this issue Jun 19, 2019 · 9 comments
Open
1 of 4 tasks

Forgone caching in cycles caused much overflow in trait solving #61960

pnkfelix opened this issue Jun 19, 2019 · 9 comments
Assignees
Labels
A-trait-system Area: Trait system metabug Issues about issues themselves ("bugs about bugs") P-medium Medium priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@pnkfelix
Copy link
Member

pnkfelix commented Jun 19, 2019

We believe PR #60444 injected a number of regressions of the form "overflow evaluating requirement [...]".

(PR #60444 also injected a compile-time performance regression; that arguably distinct issue is tracked in issue #60846.)

This issue is meant to collect the cases where there was some sort of "overflow evaluating requirement" that was injected by PR #60444. (It is possible that many (or even all) such cases are resolved by follow-up PR #61754. I'll be beta-nominating that PR on its own so that we can evaluate that question in the compiler-team meeting.)

Update: adding list of cases to investigate:

@pnkfelix
Copy link
Member Author

In case its not clear from my description: It is possible that this issue is entirely resolved by PR #61754, at least on the nightly channel. This umbrella issue is meant to be a place where I can make a list of all the relevant regressions and evaluate whether PR #61754 fixed them, which may inform a future decision on whether or not to beta-backport that PR.

@pnkfelix
Copy link
Member Author

pnkfelix commented Jun 19, 2019

Hmm, I may have been overly hasty in creating a fresh umbrella issue to track "all" the regressions here. Now that I look again at the list, and at the cross-references to PR #60444, it seems like issue #61472 may be the only issue on the Rust repo here? (I do believe that rust-lang/rust-analyzer#1283 may be another instance of this issue, but that isn't an issue on the rust-lang/rust repo, so it seems a little silly to try to include it on this list...)

@Centril Centril added I-compiletime Issue: Problems and improvements with respect to compile times. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. I-nominated labels Jun 19, 2019
@matklad
Copy link
Member

matklad commented Jun 19, 2019

I've tried rustc 1.37.0-nightly (04a3dd8a8 2019-06-18) and it still takes unreasonable time to compile rust-analyzer (this commit specifically). I don't know if the compilation succeeds or fails: it has been going on for 10 minutes already.

@matklad
Copy link
Member

matklad commented Jun 19, 2019

It overflowed half an hour later

@pnkfelix
Copy link
Member Author

Note: The compile-time performance regression was/is meant to be tracked by issue #60846. (And maybe we need to open a fresh such issue, since #60846 was closed by PR #61754 )

This issue is just meant to track "overflow evaluating requirement" diagnostics that we believe were injected by #60444.

@pnkfelix pnkfelix removed the I-compiletime Issue: Problems and improvements with respect to compile times. label Jun 20, 2019
@pnkfelix
Copy link
Member Author

triage: P-high, removing nomination.

@pnkfelix pnkfelix added P-high High priority metabug Issues about issues themselves ("bugs about bugs") and removed I-nominated labels Jun 20, 2019
@pnkfelix pnkfelix self-assigned this Jun 27, 2019
@pnkfelix
Copy link
Member Author

Unassigning self; I still think this is important, but I'm not going to be able to address it, at least not until I return from leave in September.

@nagisa
Copy link
Member

nagisa commented Jul 18, 2019

Pre-triage visit: Doubt this will be looked at before vacation spree ends, but if you want to give it a shot, by all means do so.

@jonas-schievink jonas-schievink added the A-trait-system Area: Trait system label Jul 26, 2019
@nikomatsakis nikomatsakis self-assigned this Aug 15, 2019
@pnkfelix
Copy link
Member Author

visiting for triage. Downgrading to P-medium and re-assigning back to self.

@pnkfelix pnkfelix added P-medium Medium priority and removed P-high High priority labels Sep 26, 2019
@pnkfelix pnkfelix assigned pnkfelix and unassigned nikomatsakis Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-trait-system Area: Trait system metabug Issues about issues themselves ("bugs about bugs") P-medium Medium priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

6 participants