Skip to content

Don't allow impls to force public types #11019

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

Merged
merged 1 commit into from
Dec 18, 2013

Conversation

alexcrichton
Copy link
Member

This code in resolve accidentally forced all types with an impl to become
public. This fixes it by default inheriting the privacy of what was previously
there and then becoming true if nothing else exits.

Closes #10545

This code in resolve accidentally forced all types with an impl to become
public. This fixes it by default inheriting the privacy of what was previously
there and then becoming `true` if nothing else exits.

Closes rust-lang#10545
bors added a commit that referenced this pull request Dec 18, 2013
This code in resolve accidentally forced all types with an impl to become
public. This fixes it by default inheriting the privacy of what was previously
there and then becoming `true` if nothing else exits.

Closes #10545
@bors bors closed this Dec 18, 2013
@bors bors merged commit eabf11b into rust-lang:master Dec 18, 2013
@alexcrichton alexcrichton deleted the issue-10545 branch December 19, 2013 07:50
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jun 30, 2023
[`ptr_arg`]: Don't lint when return type uses `Cow`'s lifetime

Closes rust-lang#9218

changelog: [`ptr_arg`]: Don't lint when return type uses `Cow`'s lifetime
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

privacy exposure bug when struct has field(s) *and* an impl
3 participants