Make fields in std::comm private #9935
Closed
Conversation
This file contains 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
|
This is working towards #4386. |
bors
added a commit
that referenced
this pull request
Oct 18, 2013
|
@reedlepee123 you should configure your email address with git in order to get proper attribution. This commit is attributed to |
|
@brson I believe we did that step, but not until after making the commit in this PR. Future commits shouldn't have that problem. |
flip1995
pushed a commit
to flip1995/rust
that referenced
this pull request
Dec 17, 2022
Don't lint `from_over_into` for opaque types fixes rust-lang#9935 This is stalled until the next sync. The impl in question can't be written on the pinned nightly. changelog: Don't lint `from_over_into` for opaque types
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.