-
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
Check privacy of trait items in all contexts #41332
Conversation
r? @arielb1 (rust_highfive has picked a reviewer for you, use r? to override) |
r? @eddyb |
The changes LGTM, started a crater run to see if there's any real impact. |
Sadly, Crater now outputs |
Paging @brson again, to make sure he sees it when he gets back. |
@eddyb Did you try again since? |
@bors r+ |
📌 Commit 4f7ab0e has been approved by |
Check privacy of trait items in all contexts Fixes rust-lang#28514 This is a sufficiently rare scenario and it's currently guarded by `private_in_public` lint, so it shouldn't be a [breaking-change] in practice.
⌛ Testing commit 4f7ab0e with merge c53bc6d... |
💔 Test failed - status-travis |
Conflict with recently merged #41494, will fix today. |
@bors r- |
@bors r=eddyb |
📌 Commit 4bd417e has been approved by |
⌛ Testing commit 4bd417e with merge a268165... |
💔 Test failed - status-appveyor |
Probably spurious, though odd. Filed #41545 to track this. @bors retry
|
Check privacy of trait items in all contexts Fixes #28514 This is a sufficiently rare scenario and it's currently guarded by `private_in_public` lint, so it shouldn't be a [breaking-change] in practice.
☀️ Test successful - status-appveyor, status-travis |
Type privacy polishing Various preparations before implementing rust-lang/rfcs#2145 containing final minor breaking changes (mostly for unstable code or code using `allow(private_in_public)`). (Continuation of #42125, #44633 and #41332.) It would be good to run crater on this. r? @eddyb
Fixes #28514
This is a sufficiently rare scenario and it's currently guarded by
private_in_public
lint, so it shouldn't be a [breaking-change] in practice.