-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Private-in-public lints implementation #111801
Conversation
@rustbot author |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
fd748ba
to
99cc56d
Compare
This comment has been minimized.
This comment has been minimized.
@rustbot ready |
This comment was marked as resolved.
This comment was marked as resolved.
24e5d3a
to
051c5bf
Compare
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
1 similar comment
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (36c03d72fa8b8bf825de72a5154565aa26707d18): 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: 647.255s -> 647.39s (0.02%) |
r=me after extending the comment in #111801 (comment) and squashing commits. |
@bors r+ rollup=maybe |
☀️ Test successful - checks-actions |
Finished benchmarking commit (77dba22): 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.
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: 650.784s -> 647.92s (-0.44%) |
@rustbot label: +perf-regression-triaged |
…ility This commit reverts a change made in rust-lang#111425. It was believed that this change was necessary for implementing type privacy lints, but rust-lang#111801 showed that it was not necessary. Quite opposite, the revert fixes some issues.
privacy: Type privacy lints fixes and cleanups See individual commits. Follow up to rust-lang#111801.
privacy: Type privacy lints fixes and cleanups See individual commits. Follow up to rust-lang/rust#111801.
Next part of RFC #48054.
r? @petrochenkov