-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Fixup: filter().is_none()
-> !any()
#79806
Conversation
r? @oli-obk (rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ rollup |
📌 Commit 9cc563b has been approved by |
☀️ Test successful - checks-actions |
field.vis.is_accessible_from(tcx.parent_module(pat.hir_id).to_def_id(), tcx) | ||
}) | ||
.is_none(); | ||
let no_accessible_unmentioned_fields = !unmentioned_fields.iter().any(|(field, _)| { |
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.
Would it make sense for an iterator to have a convenience none()
method that does the same as !any()
? We have such methods for any
and all
, seems logical to have it for none
as well.
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.
Feel free to open an issue or to propose a PR with an unstable implementation
No description provided.