-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Represent hir::TraitBoundModifiers
as distinct parts in HIR
#131982
Represent hir::TraitBoundModifiers
as distinct parts in HIR
#131982
Conversation
rustbot has assigned @GuillaumeGomez. Use |
Should probably be reviewed by someone on the compiler side, though feedback is obviously useful for the rustdoc and clippy sides. r? compiler |
This comment has been minimized.
This comment has been minimized.
04e48a4
to
6707086
Compare
☔ The latest upstream changes (presumably #131988) 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.
This is basically #119163 but now for HIR, so +1 from me.
r=me after rebase and nitpicks addressed
6707086
to
533db1d
Compare
This comment has been minimized.
This comment has been minimized.
533db1d
to
e90f8e1
Compare
This comment has been minimized.
This comment has been minimized.
e90f8e1
to
b6e4fca
Compare
@bors r+ |
Suspecting this based on #132018 (comment) @bors r- |
@bors try |
…difiers, r=<try> Represent `hir::TraitBoundModifiers` as distinct parts in HIR Stop squashing distinct `polarity` and `constness` into a single `hir::TraitBoundModifier`. This PR doesn't attempt to handle all the corner cases correctly, since the old code certainly did not either; but it should be much easier for, e.g., rustc devs working on diagnostics, or clippy devs, to actually handle constness and polarity correctly. try-job: x86_64-gnu-stable
It's 100% this PR: The HIR stats for |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
b6e4fca
to
febb3f7
Compare
Changes to the size of AST and/or HIR nodes. cc @nnethercote |
While we're at it, let's maybe perf test the
|
This comment has been minimized.
This comment has been minimized.
Seems like rust-timer doesn't like Alrighty then, @bors r+ rollup=iffy |
☀️ Test successful - checks-actions |
Finished benchmarking commit (e1f3068): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -0.4%, secondary -0.7%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResults (secondary -3.8%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 780.01s -> 781.732s (0.22%) |
Queued aa43197 with parent 814df6e, future comparison URL. |
Stop squashing distinct
polarity
andconstness
into a singlehir::TraitBoundModifier
.This PR doesn't attempt to handle all the corner cases correctly, since the old code certainly did not either; but it should be much easier for, e.g., rustc devs working on diagnostics, or clippy devs, to actually handle constness and polarity correctly.
try-job: x86_64-gnu-stable