Detect bad number of generics caused by bad derive - #160695
Merged
Merged
Conversation
Collaborator
|
HIR ty lowering was modified cc @fmease |
This comment has been minimized.
This comment has been minimized.
CenTdemeern1
reviewed
Aug 7, 2026
estebank
force-pushed
the
issue-160463
branch
from
September 15, 2026 22:04
b7358ef to
7f323b4
Compare
This comment has been minimized.
This comment has been minimized.
estebank
force-pushed
the
issue-160463
branch
2 times, most recently
from
September 20, 2026 18:21
d717072 to
a8a03d8
Compare
This comment has been minimized.
This comment has been minimized.
Zalathar
added a commit
to Zalathar/rust
that referenced
this pull request
Sep 21, 2026
…chenkov Do not continue past `rustc_resolve` when encountering duplicated items Duplicated items cause *lots* of confusing knock down errors. This change side-steps some known ICEs, and reduces the verbosity of crates with duplicated items at the cost of not emitting every error that we could. Noticed just how problematic these can be while looking at rust-lang#160695, as `#[derive]`s are particularly prone to the kind of confusion these duplicates cause. Fix rust-lang#120873, fix rust-lang#123690. r? @petrochenkov
JonathanBrouwer
added a commit
to JonathanBrouwer/rust
that referenced
this pull request
Sep 21, 2026
…chenkov Do not continue past `rustc_resolve` when encountering duplicated items Duplicated items cause *lots* of confusing knock down errors. This change side-steps some known ICEs, and reduces the verbosity of crates with duplicated items at the cost of not emitting every error that we could. Noticed just how problematic these can be while looking at rust-lang#160695, as `#[derive]`s are particularly prone to the kind of confusion these duplicates cause. Fix rust-lang#120873, fix rust-lang#123690. r? @petrochenkov
JonathanBrouwer
added a commit
to JonathanBrouwer/rust
that referenced
this pull request
Sep 21, 2026
…chenkov Do not continue past `rustc_resolve` when encountering duplicated items Duplicated items cause *lots* of confusing knock down errors. This change side-steps some known ICEs, and reduces the verbosity of crates with duplicated items at the cost of not emitting every error that we could. Noticed just how problematic these can be while looking at rust-lang#160695, as `#[derive]`s are particularly prone to the kind of confusion these duplicates cause. Fix rust-lang#120873, fix rust-lang#123690. r? @petrochenkov
rust-bors Bot
pushed a commit
that referenced
this pull request
Sep 21, 2026
Rollup merge of #162831 - estebank:duplicated-items, r=petrochenkov Do not continue past `rustc_resolve` when encountering duplicated items Duplicated items cause *lots* of confusing knock down errors. This change side-steps some known ICEs, and reduces the verbosity of crates with duplicated items at the cost of not emitting every error that we could. Noticed just how problematic these can be while looking at #160695, as `#[derive]`s are particularly prone to the kind of confusion these duplicates cause. Fix #120873, fix #123690. r? @petrochenkov
pull Bot
pushed a commit
to xtqqczze/rust-lang-miri
that referenced
this pull request
Sep 22, 2026
Do not continue past `rustc_resolve` when encountering duplicated items Duplicated items cause *lots* of confusing knock down errors. This change side-steps some known ICEs, and reduces the verbosity of crates with duplicated items at the cost of not emitting every error that we could. Noticed just how problematic these can be while looking at rust-lang/rust#160695, as `#[derive]`s are particularly prone to the kind of confusion these duplicates cause. Fix rust-lang/rust#120873, fix rust-lang/rust#123690. r? @petrochenkov
estebank
force-pushed
the
issue-160463
branch
from
September 25, 2026 16:07
a8a03d8 to
d0ca44e
Compare
Collaborator
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
Contributor
Author
|
@petrochenkov addressed your comments in the last commit (and shortened the label). |
Contributor
|
r=me after squashing commits. |
Collaborator
|
Reminder, once the PR becomes ready for a review, use |
estebank
force-pushed
the
issue-160463
branch
from
September 25, 2026 21:38
d0ca44e to
e7ca4a4
Compare
When a derive macro expands the annotated item's name directly using `quote!`, it keep the item's Span context (instead of having a new context). This means that the generic Span context machinery which provides feedback that an error happened due to a derive doesn't kick in. If a derive macro isn't written to take into account the existence of type parameters, an error for "mismatched number of type parameters" will be emitted. We now detect the case when this happens due to the derive macro, and customize the output to point that out, as well as avoid giving suggestions that will always be wrong.
estebank
force-pushed
the
issue-160463
branch
from
September 25, 2026 21:43
e7ca4a4 to
49276b0
Compare
Contributor
Author
|
@bors r=petrochenkov |
Contributor
Contributor
|
This pull request was unapproved. |
estebank
force-pushed
the
issue-160463
branch
from
September 26, 2026 01:06
565857b to
49276b0
Compare
Contributor
Author
|
@bors r=petrochenkov |
Contributor
rust-bors Bot
pushed a commit
that referenced
this pull request
Sep 26, 2026
Rollup of 13 pull requests Successful merges: - #160695 (Detect bad number of generics caused by bad derive) - #162883 (No longer auto-inline `f16` and `f128` on well-supported platforms) - #163133 ([rustdoc] Fix invalid jump to def link when `#[rustc_allow_incoherent_impl]` is involved) - #163215 (Fix suggestion for Option to bool with proper precedence handling) - #163266 (More deferred liveness cleanups) - #163274 (Support -Z merge-functions with gcc and add stack-protector asm tests) - #163290 (Merge `ForceWarning`/`Allow`/`Expect` into `Warning`) - #163298 (Don't emit sugg for pub-reexport extern std) - #163312 (Add rustdoc regression test for glob import of a crate that re-exports) - #163357 (Borrowck cleanups part trois) - #161710 (Stabilize `mem::conjure_zst`) - #163332 (Add some docs to `Global`) - #163362 (simplify ndk compiler test)
rust-bors Bot
pushed a commit
that referenced
this pull request
Sep 26, 2026
Rollup merge of #160695 - estebank:issue-160463, r=petrochenkov Detect bad number of generics caused by bad derive When a derive macro expands the annotated item's name directly using `quote!`, it keep the item's Span context (instead of having a new context). This means that the generic Span context machinery which provides feedback that an error happened due to a derive doesn't kick in. If a derive macro isn't written to take into account the existence of type parameters, an error for "mismatched number of type parameters" will be emitted. We now detect the case when this happens due to the derive macro, and customize the output to point that out, as well as avoid giving suggestions that will always be wrong. Partially address #160463 (this doesn't detect a nameres error caused by referencing type parameter within a derive). ``` error[E0107]: missing generics for enum `A` --> bar.rs:8:6 | 7 | #[derive(A)] | - it looks like this derive macro might not support items with generic parameters 8 | enum A<T> { | ^ ``` r? @petrochenkov
pull Bot
pushed a commit
to LeeeeeeM/miri
that referenced
this pull request
Sep 27, 2026
Rollup of 13 pull requests Successful merges: - rust-lang/rust#160695 (Detect bad number of generics caused by bad derive) - rust-lang/rust#162883 (No longer auto-inline `f16` and `f128` on well-supported platforms) - rust-lang/rust#163133 ([rustdoc] Fix invalid jump to def link when `#[rustc_allow_incoherent_impl]` is involved) - rust-lang/rust#163215 (Fix suggestion for Option to bool with proper precedence handling) - rust-lang/rust#163266 (More deferred liveness cleanups) - rust-lang/rust#163274 (Support -Z merge-functions with gcc and add stack-protector asm tests) - rust-lang/rust#163290 (Merge `ForceWarning`/`Allow`/`Expect` into `Warning`) - rust-lang/rust#163298 (Don't emit sugg for pub-reexport extern std) - rust-lang/rust#163312 (Add rustdoc regression test for glob import of a crate that re-exports) - rust-lang/rust#163357 (Borrowck cleanups part trois) - rust-lang/rust#161710 (Stabilize `mem::conjure_zst`) - rust-lang/rust#163332 (Add some docs to `Global`) - rust-lang/rust#163362 (simplify ndk compiler test)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
View all comments
When a derive macro expands the annotated item's name directly using
quote!, it keep the item's Span context (instead of having a new context). This means that the generic Span context machinery which provides feedback that an error happened due to a derive doesn't kick in.If a derive macro isn't written to take into account the existence of type parameters, an error for "mismatched number of type parameters" will be emitted. We now detect the case when this happens due to the derive macro, and customize the output to point that out, as well as avoid giving suggestions that will always be wrong.
Partially address #160463 (this doesn't detect a nameres error caused by referencing type parameter within a derive).
r? @petrochenkov