Skip to content

fix(rustc_hir_analysis): handle Node::Synthetic in diagnostic_hir_wf_check#159627

Open
DAstapov wants to merge 2 commits into
rust-lang:mainfrom
DAstapov:fix/159557
Open

fix(rustc_hir_analysis): handle Node::Synthetic in diagnostic_hir_wf_check#159627
DAstapov wants to merge 2 commits into
rust-lang:mainfrom
DAstapov:fix/159557

Conversation

@DAstapov

@DAstapov DAstapov commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Closes #159557
Closes #148630

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jul 20, 2026
@rustbot

rustbot commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Thanks for the pull request, and welcome! The Rust Project is excited to review your changes, and you should hear from @jieyouxu (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

  • @rustbot author: the review is finished, PR author should check the comments and take action accordingly
  • @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue
Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: compiler
  • compiler expanded to 74 candidates
  • Random selection from 17 candidates

@rust-log-analyzer

This comment has been minimized.

@rustbot

rustbot commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

This PR changes a file inside tests/crashes. If a crash was fixed, please move into the corresponding ui subdir and add 'Fixes #' to the PR description to autoclose the issue upon merge.

//! must not ICE in HIR wf-checking when the next solver is enabled.
//@ compile-flags: -Znext-solver=globally
//@ edition: 2024
//@ dont-require-annotations: ERROR

@jieyouxu jieyouxu Jul 21, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test is only needed to verify that no ICE is issued during compilation, and since the test produces many identical errors, I decided not to add explicit //~^ ERROR annotations, because the output is already checked via the .stderr file.
I'm not sure what the correct approach is here.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should just use normal error annotations and not ignore them. The test harness already will assert the compiler normally errors and doesn't ICE.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[ICE]: next solver: Unexpected node Synthetic ICE: Unexpected node Synthetic

4 participants