expand: More precise locations for expansion-time lints #73178
Merged
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.
First commit: a macro expansion doesn't have a
NodeId
associated with it, but it has a parentDefId
which we can use for linting.The observable effect is that lints associated with macro expansions can now be
allow
ed at finer-grained level than whole crate.Second commit: each macro definition has a
NodeId
which we can use for linting, unless that macro definition was decoded from other crate.