-
Notifications
You must be signed in to change notification settings - Fork 1.7k
SpanlessEq
improvements
#10478
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SpanlessEq
improvements
#10478
Conversation
r? @xFrednet (rustbot has picked a reviewer for you, use r? to override) |
c368649
to
867b19b
Compare
Hey, I have a busy week ahead of me. I'll review this next week, when I have a bit more time. Hope that's okay with you :) Edit: It took a month, sorry! |
☔ The latest upstream changes (presumably #10528) made this pull request unmergeable. Please resolve the merge conflicts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Just two small questions, one is posted as a comment.
Have you measured, how much this change effects performance? I'd guess that it should not be significant, but it would still be good to check before merging it.
Also, thanks for being patient when it comes to the review! I had exams and really needed a break afterwards. The next review or r+ should be much faster 🙃
@Jarcho Have you seen the question in my review comment?
Once that is answered and the PR has been rebased, it should be ready for bors :) |
Ping @Jarcho, I'm currently triaging my PRs. This one was already approved and only requires a rebase. Would you mind doing so? Then you can |
…ro expansion and `cfg`ed statements.
Sorry. I kept telling myself I would deal with it 'later', and later has finally come. Don't ask me about when 'someday' is coming though. I'm not looking forward to that one. Dogfood runs in approximately the same amount of time. So no obvious perf issues. |
* Don't consider expansions of different macros to be the same, even if they expand to the same tokens * Don't consider `cfg!` expansions to be equal if they check different configs.
@bors r=xFrednet |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
fixes #9775
Also includes a simplification to
consts::constant
's interface since I was already touching the code.At the start of
eq_expr
the check:was removed. This was added in 49e2501 to handle
cfg
macros. This is better handled by the newly addedcheck_ctxt
.changelog: [various lints]: Don't consider different
cfg!
expansions to be the same unless they are for the same config.changelog: [various lints]: Don't consider the expansion of two different macros to be equal, even when they expand to the same token sequence.
changelog: [various lints]: Don't consider two blocks to be equal if they contain disabled code or empty macro expansions, unless those section contain the exact same token sequence.