Update function objects section to the new format #648
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also fixes a bug in the return type of logical_and and logical_or. Closes #646.
The return types of the
void
specializations ofmaximum
andminimum
may require further discussion. Prior to this change, the specification didn't say exactly which operator(s) would be used to determine ordering, and so I tried to honor that in this new wording.When we introduced the prior wording there was some discussion of trying to align with
std::min
andstd::max
(see #285 (comment)). It we want to describe the behavior in terms of equivalent statements, I think the fix is to say:minimum
andmaximum
requireT
to beLessThanComparable
.minimum
returns(b < a) ? b : a
.maximum
returns(a < b) ? b : a
.