Skip to content

Conversation

@ChayimFriedman2
Copy link
Contributor

Previously all lints were assumed to be #[warn], and we had a hand-coded list of #[allow] exceptions. Now the severity is autogenerated from rustdoc output.

Also support lints that change status between editions, and the warnings lint group.

Fixes #18462.

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Nov 2, 2024
//! The edition of the Rust language used in a crate.
// Ideally this would be defined in the span crate, but the dependency chain is all over the place
// wrt to span, parser and syntax.
// This should live in a separate crate because we use it in both actual code and codegen.
Copy link
Member

Choose a reason for hiding this comment

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

Can we just include! this file in xtask instead? I personally don't really like this small thing being a crate. Or just duplicate what we need given its not much

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't want to duplicate because then adding edition will need to touch both. But include!() seems fine.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It works for rustc but r-a is unable to find the file both with #[path = "..."] mod edition; and with include!(), do you know why?

Copy link
Member

@Veykril Veykril Dec 9, 2024

Choose a reason for hiding this comment

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

Ahaha, right. This fails in r-a because the include lies outside of the source root of the crate itself so we fail to resolve the path... This is one of the outstanding problems with our VFS system

In that case I guess we can stay with the crate for now

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

@rustbot ready

@Veykril Veykril added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 7, 2024
@ChayimFriedman2 ChayimFriedman2 force-pushed the proper-lint-severity branch 2 times, most recently from e30ed15 to 7aebc12 Compare December 9, 2024 23:39
@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Dec 9, 2024
@Veykril Veykril added this pull request to the merge queue Dec 11, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 11, 2024
@bors
Copy link
Contributor

bors commented Dec 11, 2024

☔ The latest upstream changes (presumably #18662) made this pull request unmergeable. Please resolve the merge conflicts.

Previously all lints were assumed to be `#[warn]`, and we had a hand-coded list of `#[allow]` exceptions. Now the severity is autogenerated from rustdoc output.

Also support lints that change status between editions, and the `warnings` lint group.
@ChayimFriedman2
Copy link
Contributor Author

@Veykril can you re-approve? Thanks.

@Veykril Veykril enabled auto-merge December 11, 2024 18:55
@Veykril Veykril added this pull request to the merge queue Dec 11, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 11, 2024
@ChayimFriedman2
Copy link
Contributor Author

I cannot reproduce the failure locally - @Veykril do you have any idea what's going on?

@lnicola

This comment was marked as off-topic.

@lnicola lnicola added this pull request to the merge queue Dec 11, 2024
Merged via the queue into rust-lang:master with commit b707b5a Dec 11, 2024
9 checks passed
@ChayimFriedman2 ChayimFriedman2 deleted the proper-lint-severity branch December 11, 2024 21:00
@Veykril
Copy link
Member

Veykril commented Dec 12, 2024

Oh no are we still racing in that test?

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug in handling unsafe_op_in_unsafe_fn

5 participants