Difference between revisions of "cpp/iterator/indirect strict weak order"
(~ apply P2997R1 as DR20) |
(c -> c/core.) |
||
Line 1: | Line 1: | ||
{{cpp/title|indirect_strict_weak_order}} | {{cpp/title|indirect_strict_weak_order}} | ||
{{cpp/iterator/navbar}} | {{cpp/iterator/navbar}} | ||
− | {{ | + | {{ddcl|header=iterator|since=c++20|1= |
− | + | ||
− | + | ||
template< class F, class I1, class I2 = I1 > | template< class F, class I1, class I2 = I1 > | ||
concept indirect_strict_weak_order = | concept indirect_strict_weak_order = | ||
Line 9: | Line 7: | ||
std::indirectly_readable<I2> && | std::indirectly_readable<I2> && | ||
std::copy_constructible<F> && | std::copy_constructible<F> && | ||
− | std::strict_weak_order<F&, /*indirect-value-t*/<I1>, /*indirect-value-t*/<I2>> && | + | std::strict_weak_order |
+ | <F&, /*indirect-value-t*/<I1>, /*indirect-value-t*/<I2>> && | ||
std::strict_weak_order | std::strict_weak_order | ||
<F&, /*indirect-value-t*/<I1>, std::iter_reference_t<I2>> && | <F&, /*indirect-value-t*/<I1>, std::iter_reference_t<I2>> && | ||
Line 17: | Line 16: | ||
<F&, std::iter_reference_t<I1>, std::iter_reference_t<I2>>; | <F&, std::iter_reference_t<I1>, std::iter_reference_t<I2>>; | ||
}} | }} | ||
− | |||
The concept {{tt|indirect_strict_weak_order}} specifies requirements for algorithms that call strict weak orders as their arguments. The key difference between this concept and {{lc|std::strict_weak_order}} is that it is applied to the types that {{tt|I1}} and {{tt|I2}} references, rather than {{tt|I1}} and {{tt|I2}} themselves. | The concept {{tt|indirect_strict_weak_order}} specifies requirements for algorithms that call strict weak orders as their arguments. The key difference between this concept and {{lc|std::strict_weak_order}} is that it is applied to the types that {{tt|I1}} and {{tt|I2}} references, rather than {{tt|I1}} and {{tt|I2}} themselves. | ||
Line 23: | Line 21: | ||
===Defect reports=== | ===Defect reports=== | ||
{{dr list begin}} | {{dr list begin}} | ||
− | {{dr list item|paper=P2609R3|std=C++20|before=some requirements were defined in terms of {{c|std::iter_value_t<I>&}} | + | {{dr list item|paper=P2609R3|std=C++20|before=some requirements were defined in terms of<br>{{c/core|std::iter_value_t<I>&}} which mishandled projections<br>resulting in incompatibility with strict weak order {{c/core|F&}}|after=defined in terms of<br>{{c/core|/*indirect-value-t*/<I>}} to<br>correctly handle such projections}} |
− | {{dr list item|paper=P2997R1|std=C++20|before={{tt|indirect_strict_weak_order}} required {{c|F&}} to satisfy {{lconcept|strict_weak_order}} with | + | {{dr list item|paper=P2997R1|std=C++20|before={{tt|indirect_strict_weak_order}} required {{c/core|F&}} to satisfy<br>{{lconcept|strict_weak_order}} with {{c/core|std::iter_common_reference_t<I>}}|after=does not require}} |
{{dr list end}} | {{dr list end}} | ||
{{langlinks|de|es|fr|it|ja|pt|ru|zh}} | {{langlinks|de|es|fr|it|ja|pt|ru|zh}} |
Latest revision as of 17:01, 13 October 2024
Defined in header <iterator>
|
||
template< class F, class I1, class I2 = I1 > concept indirect_strict_weak_order = |
(since C++20) | |
The concept indirect_strict_weak_order
specifies requirements for algorithms that call strict weak orders as their arguments. The key difference between this concept and std::strict_weak_order is that it is applied to the types that I1
and I2
references, rather than I1
and I2
themselves.
[edit] Defect reports
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
DR | Applied to | Behavior as published | Correct behavior |
---|---|---|---|
P2609R3 | C++20 | some requirements were defined in terms of std::iter_value_t<I>& which mishandled projections resulting in incompatibility with strict weak order F& |
defined in terms of /*indirect-value-t*/<I> to correctly handle such projections |
P2997R1 | C++20 | indirect_strict_weak_order required F& to satisfystrict_weak_order with std::iter_common_reference_t<I>
|
does not require |