-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Port #[rustc_layout_scalar_valid_range_start/end]
to the new attrib…
#142921
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
base: master
Are you sure you want to change the base?
Port #[rustc_layout_scalar_valid_range_start/end]
to the new attrib…
#142921
Conversation
|
Some changes occurred in compiler/rustc_attr_data_structures Changes to the size of AST and/or HIR nodes. cc @nnethercote Some changes occurred in compiler/rustc_attr_parsing Some changes occurred in compiler/rustc_passes/src/check_attr.rs |
46ea3f1
to
9102b14
Compare
@@ -85,7 +85,7 @@ hir-stats FnDecl 120 (NN.N%) 3 40 | |||
hir-stats FieldDef 128 (NN.N%) 2 64 | |||
hir-stats GenericArgs 144 (NN.N%) 3 48 | |||
hir-stats Variant 144 (NN.N%) 2 72 | |||
hir-stats Attribute 160 (NN.N%) 4 40 | |||
hir-stats Attribute 192 (NN.N%) 4 48 |
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 because the new attribute has both a u128
and a span
. Is this a problem? If so I can box the u128
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.
I've kicked off a perf-run, let's see what happens.
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.
Attributes aren't that common, so it's not too important. Having said that, it looks like boxing the u128
s would be really easy, so it's probably worth doing that.
@@ -41,4 +41,5 @@ extern "C" {} | |||
|
|||
#[rustc_layout_scalar_valid_range_start(0suffix)] | |||
//~^ ERROR invalid suffix `suffix` for number literal | |||
//~| ERROR malformed `rustc_layout_scalar_valid_range_start` attribute input |
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.
I don't really like this change, but not sure how to fix it. I think my new lint is the one which should not be triggered, but I just get an attribute with an empty list with no way to detect that it is empty because something previously errored. @jdonszelmann advice?
…ute parsing infrastructure Signed-off-by: Jonathan Brouwer <[email protected]>
9102b14
to
49398cf
Compare
…t, r=jdonszelmann Fix comment on NoMangle Fix comment on NoMangle. This was discussed in comments of rust-lang#142823 (comment) and rust-lang#142921
@bors2 try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
Port `#[rustc_layout_scalar_valid_range_start/end]` to the new attrib… Ports `rustc_layout_scalar_valid_range_start` and `rustc_layout_scalar_valid_range_end` to the new attribute parsing infrastructure for #131229 (comment) r? `@jdonszelmann`
Queued 600a41a with parent 706f244, future comparison URL. |
Rollup merge of #142922 - JonathanBrouwer:fix-rustdoc-comment, r=jdonszelmann Fix comment on NoMangle Fix comment on NoMangle. This was discussed in comments of #142823 (comment) and #142921
Ports
rustc_layout_scalar_valid_range_start
andrustc_layout_scalar_valid_range_end
to the new attribute parsing infrastructure for #131229 (comment)r? @jdonszelmann