-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix: support map_or
for or_fun_call
lint
#9689
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @flip1995 (or someone else) soon. Please see the contribution instructions for more information. |
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.
LGTM overall. Just a NIT.
e0496f2
to
1226a5a
Compare
* add `rest_arg` to pass second argument from `map_or(U, F)` * extract some procedures into closure refac: rename rest_arg/second_arg refac: organize function argument order * put `second_arg` next to `arg` argument
1226a5a
to
a41cb7a
Compare
@bors r+ Thanks! |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
fixes #8993
The methods defined in
KNOW_TYPES
, except formap_or
, accepts only one argument, so the matchingif let [arg] = args
works only for these methods.This PR adds
rest_arg
argument tocheck_general_case
method and handling of cases with two arguments to supportmap_or
.changelog:
or_fun_call
supportmap_or
rest_arg
to pass second argument frommap_or(U, F)