Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
af7af07 to
a6a436d
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Sure. Please no more obscure platform failures, please no more obscure platform failures, please no more obscure platform failures, please no more obscure platform failures... |
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.
69a1881 to
21fd14f
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
I forgor about the rustconf :) |
|
Is all good! I forgor mentioning it. But yeah, I would be fine doing r+ for non os/sys module stuff but would probably hold off on other modules for now. |
e3e3456 to
081b1b5
Compare
This comment has been minimized.
This comment has been minimized.
|
Tests are passing. I explicitly allow |
|
Thank you! And apologies for taking a while on this one. @bors r+ rollup |
|
No worries. For the rest - I've been thinking about adding |
|
So, actually, I kind of want to do the opposite: specifically enabling this lint on target-independent code, since it runs everywhere, but not on target-specific code, which will only selectively lint when it's enabled. But ultimately, the main reason why I didn't want to deal with os/sys for now is that we have other initiatives to refactor those modules and I don't want to do anything major without a larger discussion. |
std: make a lot of items crate private 1. Enabled `warn(unreachable_pub)` 2. Made a lot of things crate private, to the point when doing more required adding exceptions 3. Removed `warn(unreachable_pub)` So now this commit just tightens the current visibility without trying to enforce it. r? clarfonthey
Rollup of 5 pull requests Successful merges: - #162732 (Fix unsound dealloc of reborrows from custom allocators) - #154113 (std::net: clamp multicast ttl value to u8 max.) - #161178 (lint ineffective #[unstable] annotations on re-exports) - #161612 (std: make a lot of items crate private) - #162717 (prevent ICE from `derive` on `repr(packed)` enum)
|
Looks like there are two things: one case was missed and the lint was left enabled in some spot (despite the PR description). @bors r- |
|
This pull request was unapproved. This PR was contained in a rollup (#162737), which was unapproved. |
081b1b5 to
a2857b3
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
a2857b3 to
58ff82d
Compare
Most of them don't need to be public, but there are scenarios where thing is private on one platform but public on the other, so having a lint on all the time gets complicated. Added #![warn(unreachable_pub)] in library/std/src/lib.rs Added #[allow(unreachable_pub)] on top of std::os and std::sys specifically.
58ff82d to
0f916bb
Compare
|
Updated the description, reduced visibility in two missing cases in |
|
@bors retry |
|
❗ You can only retry pull requests that are approved and have a previously failed auto build. Hint: If you wanted to retry pull request CI instead, push the latest commit again, or close and then reopen this PR. |
|
@bors r+ rollup |
#![warn(unreachable_pub)]inlibrary/std/src/lib.rs#[allow(unreachable_pub)]on top ofstd::osandstd::sysspecifically.View all comments
r? clarfonthey