cpp/iterator/indirectly movable: Difference between revisions
From cppreference.com
m + std:: |
Andreas Krug (talk | contribs) m fmt |
||
| Line 2: | Line 2: | ||
{{cpp/iterator/navbar}} | {{cpp/iterator/navbar}} | ||
{{ddcl|header=iterator|since=c++20|1= | {{ddcl|header=iterator|since=c++20|1= | ||
template<class In, class Out> | template< class In, class Out > | ||
concept indirectly_movable = | concept indirectly_movable = | ||
std::indirectly_readable<In> && | std::indirectly_readable<In> && | ||
| Line 12: | Line 12: | ||
===See also=== | ===See also=== | ||
{{dsc begin}} | {{dsc begin}} | ||
{{dsc inc | cpp/iterator/dsc indirectly_movable_storable}} | {{dsc inc|cpp/iterator/dsc indirectly_movable_storable}} | ||
{{dsc inc | cpp/iterator/dsc indirectly_copyable}} | {{dsc inc|cpp/iterator/dsc indirectly_copyable}} | ||
{{dsc end}} | {{dsc end}} | ||
{{langlinks|es|ja|zh}} | {{langlinks|es|ja|zh}} | ||
Latest revision as of 06:16, 1 October 2023
| Defined in header <iterator>
|
||
template< class In, class Out >
concept indirectly_movable =
std::indirectly_readable<In> &&
std::indirectly_writable<Out, std::iter_rvalue_reference_t<In>>;
|
(since C++20) | |
The indirectly_movable concept specifies the relationship between an indirectly_readable type and a type that is indirectly_writable. The indirectly_writable type must be able to directly move the object that the indirectly_readable type references.
See also
(C++20) |
specifies that values may be moved from an indirectly_readable type to an indirectly_writable type and that the move may be performed via an intermediate object (concept) |
(C++20) |
specifies that values may be copied from an indirectly_readable type to an indirectly_writable type (concept) |