[stable] 1.59.0 artifacts (second round) #94265
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Some changes occurred in src/tools/clippy. cc @rust-lang/clippy |
|
rust-highfive
added
the
S-waiting-on-review
|
@bors r+ rollup=never p=100 |
|
📌 Commit 6bd1b5f has been approved by |
bors
added
S-waiting-on-bors
|
⌛ Testing commit 6bd1b5f with merge 4d4c42ee7f6e342d9e29161f020e3c3443730c7e... |
|
💔 Test failed - checks-actions |
bors
added
S-waiting-on-review
|
@bors retry macos runner missing |
bors
added
S-waiting-on-bors
|
☀️ Test successful - checks-actions |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This backports (from 1.60, landed in #93001):
return_self_not_must_usetopedanticrust-clippy#8302Per a user report on the internals feedback thread, this lint is not behaving well in 1.59.
cc @rust-lang/clippy -- this is a stable backport of a patch, which we'll likely want to land in fairly short order to be in time for the release Thursday.
This PR also includes an adjustment to the release notes to reflect "Fix invalid special casing of the unreachable! macro #93179".
r? @Mark-Simulacrum