You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* [oneDPL][doc] + limitation for permutation_iterator using
* A limitation about algorithms which work with an uninitialized storage added to introduction.rst
* Adding documentation for transform_if to guide (#1317)
---------
Signed-off-by: Dan Hoeflinger <[email protected]>
Co-authored-by: MikeDvorskiy <[email protected]>
Copy file name to clipboardexpand all lines: documentation/library_guide/introduction.rst
+3
Original file line number
Diff line number
Diff line change
@@ -138,6 +138,9 @@ Known Limitations
138
138
the dereferenced value type of the provided iterators should satisfy the ``DefaultConstructible`` requirements.
139
139
* For ``remove``, ``remove_if``, ``unique`` the dereferenced value type of the provided
140
140
iterators should be ``MoveConstructible``.
141
+
* The algorithms which process uninitialized storage: ``uninitialized_copy``, ``uninitialized_copy_n``, ``uninitialized_fill``, ``uninitialized_fill_n``, ``uninitialized_fill_n``, ``uninitialized_move``, ``uninitialized_move_n``, ``uninitialized_default_construct``, ``uninitialized_default_construct_n``, ``uninitialized_value_construct``, ``uninitialized_value_construct_n``
142
+
should be called with a device policy when using device data and should be called with a host policy when using host data. Otherwise, the result is undefined.
143
+
* The algorithms which destroy data: ``destroy``, ``destroy_n``, should be called with a host policy when using host data which was initialized on the host, and should be called with a device policy when using device data which was initialized on the device. Otherwise, the result is undefined.
0 commit comments