-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
remove multiple unhelpful reason = "..." values from #[unstable(...)] invocations
#151228
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
| } | ||
| } | ||
|
|
||
| #[unstable(reason = "not public", issue = "none", feature = "fd_read")] |
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.
I had to dig into this one, as it wasn't immediately obvious. Nothing enables this feature and the struct is ultimately not publicly accessible thru anything, so I'm confident that the attribute can be removed without issue.
|
I would've sworn the reason was mandatory, but I guess that's not the case given passing CI. While I think it would be best to have the true reason for everything, I agree that the status quo is effectively useless. I do think that "this is an implementation detail"-style messages should be left. @bors r+ rollup |
This comment has been minimized.
This comment has been minimized.
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing defdb83 (parent) -> 844f131 (this PR) Test differencesShow 2 test diffs2 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 844f13103a64a898897174b19811b3bfb093dc53 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (844f131): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary 2.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 475.301s -> 472.032s (-0.69%) |
…=scottmcm remove `#[deprecated]` from unstable & internal `SipHasher13` and `24` types These types are unstable and `doc(hidden)` (under the internal feature `hashmap_internals`). Deprecating them only adds noise (`#[allow(deprecated)]`) to all places where they are used, so this PR removes the deprecation attributes from them. It also includes a few other small cleanups in separate commits, including one I overlooked in rust-lang#151228.
Rollup merge of #151383 - cyrgani:no-internal-deprecation, r=scottmcm remove `#[deprecated]` from unstable & internal `SipHasher13` and `24` types These types are unstable and `doc(hidden)` (under the internal feature `hashmap_internals`). Deprecating them only adds noise (`#[allow(deprecated)]`) to all places where they are used, so this PR removes the deprecation attributes from them. It also includes a few other small cleanups in separate commits, including one I overlooked in #151228.
remove `#[deprecated]` from unstable & internal `SipHasher13` and `24` types These types are unstable and `doc(hidden)` (under the internal feature `hashmap_internals`). Deprecating them only adds noise (`#[allow(deprecated)]`) to all places where they are used, so this PR removes the deprecation attributes from them. It also includes a few other small cleanups in separate commits, including one I overlooked in rust-lang/rust#151228.
The vast majority of
#[unstable()]attributes already has no explicit reason specified. This PR removes thereason = "..."value for the following unhelpful or meaningless reasons:An example of how the message looks with and without a reason:
Most of the remaining reasons after this are something similar to "this is an implementation detail for XYZ" or "this is not public". If this PR is approved, I'll look into those next.
The PR also removes the
fd_readfeature gate. It only consists of one attribute applied to an implementation inside a module that is already private and unstable and should not be needed.