[alg.min.max] Reword min/max/minmax in modern style #6776
Conversation
|
This is all editorial, but probably a big enough change that LWG should sign off on it anyway. |
|
This doesn't exactly address #6747, which wants to replace "smaller" and "larger" with "lesser" and "greater". I want to get rid of the terms altogether and more directly explain what these algorithms do with a custom predicate and projection. In no way does (But yes - thanks - the issue and PR do seem to be at least related.) |
|
Right. Closes #6747.
Closes #6752. |
... to clarify the meaning of "smaller"/"smallest"/"larger"/"largest" with a custom comparison predicate and/or projection.
| @@ -8724,19 +8724,20 @@ | |||
| \end{itemdecl} | |||
|
|
|||
| \begin{itemdescr} | |||
| \pnum | |||
| Let \tcode{comp} be \tcode{less\{\}} | |||
There was a problem hiding this comment.
I'm not sure whether this part is editorial for legacy std versions. Since less{} is more determinate than the built-in operation when the comparison between pointers is involved.
... to clarify the meaning of "smaller"/"smallest"/"larger"/"largest" with a custom comparison predicate and/or projection by effectively replacing those terms with code.
Closes #6747.
Closes #6752.