-
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
Improve unwrap_or_else_default
when handling unwrap_or_else(XXX::new)
#8163
Improve unwrap_or_else_default
when handling unwrap_or_else(XXX::new)
#8163
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Manishearth (or someone else) soon. Please see the contribution instructions for more information. |
646192a
to
709d2ce
Compare
3304436
to
79cf412
Compare
e2c3e48
to
db236e6
Compare
unwrap_or_else_default
- WIPunwrap_or_else_default
unwrap_or_else_default
unwrap_or_else_default
when handling unwrap_or_else(XXX::new)
@bors r+ |
📌 Commit 2a47dbc has been approved by |
…hearth Improve `unwrap_or_else_default` when handling `unwrap_or_else(XXX::new)` changelog: - change `unwrap_or_else_default` to work with std constructors like `Vec::new`, `HashSet::new`, `HashMap::new`. Notes: - Code to handle detecting those constructors is already there. I moved it out to `is_default_equivalent_call`
💔 Test failed - checks-action_test |
The changelog entry has to be on the same line like the @bors retry |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
changelog: change
unwrap_or_else_default
to work with std constructors likeVec::new
,HashSet::new
,HashMap::new
.Notes:
is_default_equivalent_call