std: make a lot of items crate private - #161612
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.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
0184c8a to
fbcbb5d
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
fbcbb5d to
e3e3456
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@clarfonthey thoughts? I don't mind keep rebasing it if you need more time to review/decide, but I'm also okay with just closing it - it doesn't really affect me at least at the moment. |
|
Sorry, been scatterbrained preparing for rustconf and being at rustconf. Wanted to say essentially, I'm fine unilaterally merging this for non-os/sys modules but would probably want to hold off on those for now. |
|
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. |
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. I enabled the lint, made a lot of things private to the point that dealing with the rest required adding exceptions and disabled the lint back again.
e3e3456 to
081b1b5
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. |
|
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. |
warn(unreachable_pub)warn(unreachable_pub)So now this commit just tightens the current visibility without trying to enforce it.
View all comments
r? clarfonthey