-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Regression in nightly-2024-05-27 #126117
Labels
P-high
High priority
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
rustbot
added
the
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
label
Jun 7, 2024
probably specifically 29a630e |
JonathanBrouwer
changed the title
Regression in nightly-2024-03-18
Regression in nightly-2024-05-27
Jun 7, 2024
workingjubilee
added
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
E-needs-mcve
Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
and removed
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
labels
Jun 7, 2024
rustbot
added
the
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
label
Jun 7, 2024
I managed to reduce the example a lot. This code still shows the same behavior: pub trait Parser<E> {
fn parse(&self) -> E;
}
impl<E, T: Fn() -> E> Parser<E> for T {
fn parse(&self) -> E {
self()
}
}
pub fn recursive_fn<E>() -> impl Parser<E> {
move || {
recursive_fn().parse()
}
} |
lqd
added
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
and removed
E-needs-mcve
Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example
labels
Jun 8, 2024
oof, looks like this code will break with the new solver, too (cc @lcnr) |
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-high |
rustbot
added
P-high
High priority
and removed
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
labels
Jun 11, 2024
lqd
added
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
and removed
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
labels
Jun 11, 2024
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jun 11, 2024
Rollup merge of rust-lang#126258 - oli-obk:recursive_rpit, r=lcnr Do not define opaque types when selecting impls fixes rust-lang#126117 r? `@lcnr` for inconsistency with next solver
Reopening to track beta backport |
Backport was completed, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P-high
High priority
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
The code in my hobby project Prism compiles on stable, but not on the latest nightly.
https://github.com/JonathanBrouwer/Prism/tree/222637a80cc2bb7794d0e4f649665fdd4ca23320
Sadly the codebase is quite large and I don't really see a good way to reduce it.
I ran cargo-bisect-rustc, which got the following output: (Which is a version bump commit, which confuses me)
searched nightlies: from nightly-2024-01-01 to nightly-2024-06-07
regressed nightly: nightly-2024-03-18
searched commit range: 766bdce...eb45c84
regressed commit: 4c1b9c3
The most interesting error that is returned on nightly is:
Though multiple errors are returned. The entire error log is:
https://gist.github.com/JonathanBrouwer/33d429eab435c266029b3a0828642760
The text was updated successfully, but these errors were encountered: