-
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
min_by/max_by on iterators #1722
Labels
T-libs-api
Relevant to the library API team, which will review and decide on the RFC.
Comments
As far as I could tell, we might reuse
|
Given that all of these are already in the standard library:
I think it’s clear that |
nrc
added
the
T-libs-api
Relevant to the library API team, which will review and decide on the RFC.
label
Aug 20, 2016
Agree with @SimonSapin. Closing in favor of rust-lang/rust#35856. Thanks @phimuemue. |
bors
added a commit
to rust-lang/rust
that referenced
this issue
Sep 3, 2016
Introduce max_by/min_by on iterators See rust-lang/rfcs#1722 for reference. It seems that there is `min`, `max` (simple computation of min/max), `min_by_key`, `max_by_key` (min/max by comparing mapped values) but no `min_by` and `max_by` (min/max according to comparison function). However, e.g. on vectors or slices there is `sort`, `sort_by_key` and `sort_by`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that there is min, max (simple computation of min/max), min_by_key, max_by_key (min/max by comparing mapped values) but no min_by and max_by (min/max according to comparison function). However, e.g. on vectors or slices there is sort, sort_by_key and sort_by.
Wouldn't it be convenient to have min_by/max_by on iterators?
The text was updated successfully, but these errors were encountered: