-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Populate effective visibilities in 'rustc_privacy' #110907
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
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
This comment has been minimized.
This comment has been minimized.
This comment was marked as resolved.
This comment was marked as resolved.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@rustbot ready |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 2dde54e6fd723b4e4c394184d4317aa3152eabd7 with merge 5e51bd5d58485b696cc9637960f1b3a0542f2f6d... |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (5e51bd5d58485b696cc9637960f1b3a0542f2f6d): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis 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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 656.873s -> 657.124s (0.04%) |
💔 Test failed - checks-actions |
Let's check whether it's spurious. |
☀️ Test successful - checks-actions |
1 similar comment
☀️ Test successful - checks-actions |
@@ -310,6 +310,7 @@ where | |||
/// Real logic of both `Flatten` and `FlatMap` which simply delegate to | |||
/// this type. | |||
#[derive(Clone, Debug)] | |||
#[unstable(feature = "trusted_len", issue = "37572")] |
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.
Unexpected to see it there
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.
From what I see FlattenCompat
is in a where
clause of a public item, so it's considered leaked (reachable).
Requirements for stability attributes are pretty conservative, they are required on reachable items even if they are not nameable (exported).
Finished benchmarking commit (31a4f2d): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis 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.
CyclesResultsThis 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: 653.763s -> 653.481s (-0.04%) |
This regressed (and likely has regressed other things) |
…rochenkov Revert "Populate effective visibilities in `rustc_privacy`" This reverts commit cff85f2, cc rust-lang#110907. It needs to be fixed, but there are too many issues being reported that I wanted to put up a revert until a proper fix can be committed. Fixes a ton of issues where private but still reachable impls were missing during codegen: Fixes rust-lang#111320 Fixes rust-lang#111321 Fixes rust-lang#111334 Fixes rust-lang#111357 Fixes rust-lang#111368 Fixes rust-lang#111373 Fixes rust-lang#111377 Fixes rust-lang#111386 Fixes rust-lang#111387 `@bors` p=1 r? `@petrochenkov`
Populate effective visibilities in `rustc_privacy` (take 2) Same as rust-lang#110907 + regressions fixes. Fixes rust-lang#111359. r? `@petrochenkov`
Populate effective visibilities in `rustc_privacy` (take 2) Same as rust-lang/rust#110907 + regressions fixes. Fixes rust-lang/rust#111359. r? `@petrochenkov`
rustc_privacy: Cleanups and perf improvements to `EmbargoVisitor` Continuation of rust-lang#110907.
rustc_privacy: Cleanups and perf improvements to `EmbargoVisitor` Continuation of rust-lang/rust#110907.
Populate effective visibilities in `rustc_privacy` (take 2) Same as rust-lang/rust#110907 + regressions fixes. Fixes rust-lang/rust#111359. r? `@petrochenkov`
Next part of RFC #48054.
r? @petrochenkov