-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Fix private module loophole in the 'private type in public item' check #23290
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Now with test |
testing, ignore this triage: I-nominated (1.0 beta) |
triage: I-nominated |
triage: I-nominated |
1 similar comment
triage: I-nominated |
triage: I-nominated (1.0 beta) |
triage: P-high |
triage: I-nominated |
triage P-high |
triage: I-nominated |
triage P-high |
☔ The latest upstream changes (presumably #23265) made this pull request unmergeable. Please resolve the merge conflicts. |
rebased |
visit::walk_impl_item(self, impl_item); | ||
match impl_item.node { | ||
ast::MethodImplItem(..) | ||
if self.exported_items.contains(&impl_item.id) || |
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.
can you maybe add a comment about what's going on here? I'm not sure I understand, though I presume this is related to the rules about privacy and impls?
r+ modulo nits |
@bors r=nmatsakis 8ef2fb5237ec49ea8d27b868a29743693a3c8605 |
⌛ Testing commit 8ef2fb5 with merge 885ae98... |
💔 Test failed - auto-win-32-nopt-t |
Closes #22261 r? @nikomatsakis (+ a new test coming soon...)
Closes #22261
r? @nikomatsakis
(+ a new test coming soon...)