Skip to content

Deny warnings in the test for crates that are available on stable#155961

Open
jdonszelmann wants to merge 2 commits intorust-lang:mainfrom
jdonszelmann:deny-warnings-stable
Open

Deny warnings in the test for crates that are available on stable#155961
jdonszelmann wants to merge 2 commits intorust-lang:mainfrom
jdonszelmann:deny-warnings-stable

Conversation

@jdonszelmann
Copy link
Copy Markdown
Contributor

@jdonszelmann jdonszelmann commented Apr 29, 2026

We've got a couple of crates, like rustc_type_ir that have parts disabled on stable. I believe part of this is so, for example, rust-analyzer can use bits of the compiler. We previously allowed warnings here, and I ran into one. This denies warnings in the test that compiles these stable crates (I chose not to on the crate itself, so you don't constantly run into the warnings if you have turned that off in config.toml). This test doesn't run by default, but it does run in CI.

@rustbot rustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Apr 29, 2026
@jdonszelmann jdonszelmann changed the title Deny warnings stable Deny warnings in the test for crates that are available on stable Apr 29, 2026
@jdonszelmann jdonszelmann marked this pull request as ready for review April 29, 2026 09:33
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 29, 2026
@rustbot rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Apr 29, 2026
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Apr 29, 2026

r? @mejrs

rustbot has assigned @mejrs.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: compiler, types
  • compiler, types expanded to 73 candidates
  • Random selection from 19 candidates

@rust-log-analyzer
Copy link
Copy Markdown
Collaborator

The job x86_64-gnu-miri failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

#[cfg(feature = "nightly")]
macro_rules! generate { ($( $tt:tt )*) => { $( $tt )* } }

/// For early binders, you should first call `instantiate` before using any visitors.
Copy link
Copy Markdown
Member

@bjorn3 bjorn3 Apr 29, 2026

Choose a reason for hiding this comment

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

This should be inside the generate!() to add docs to the impl, right? Also maybe you can merge both generate!() calls together to avoid duplicating the cfg.

View changes since the review

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

Labels

A-run-make Area: port run-make Makefiles to rmake.rs 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.

5 participants