Docs: Better explanation of return values for min, max functions for the Iterator trait #39955
Conversation
Explain that a None is returned if the iterator is empty.
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @aturon (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
|
Excellent, thanks! @bors: r+ rollup |
|
📌 Commit eee6752 has been approved by |
Docs: Better explanation of return values for min, max functions for the Iterator trait Added an explanation that `None` is returned if an iterator is empty. Also added examples for `max` and `min`. I chose not to add examples for other functions like `max_by_key` etc. so that the examples stay concised and focused on the main functionality.
Docs: Better explanation of return values for min, max functions for the Iterator trait Added an explanation that `None` is returned if an iterator is empty. Also added examples for `max` and `min`. I chose not to add examples for other functions like `max_by_key` etc. so that the examples stay concised and focused on the main functionality.
|
☀️ Test successful - status-appveyor, status-travis |
Added an explanation that
Noneis returned if an iterator is empty.Also added examples for
maxandmin. I chose not to add examples for other functions likemax_by_keyetc. so that the examples stay concised and focused on the main functionality.