[oneDPL] Indirectly Device Accessible Iterator Customization Point and Public Trait#620
[oneDPL] Indirectly Device Accessible Iterator Customization Point and Public Trait#620danhoeflinger merged 60 commits intomainfrom
Conversation
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Co-authored-by: Alexey Kukanov <[email protected]>
|
@akukanov All good suggestions... applied. Thanks. |
Co-authored-by: Alexey Kukanov <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
mmichel11
left a comment
There was a problem hiding this comment.
I have some small suggestions after rereading the latest version. I am ready to approve once these are considered.
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
…edge Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Co-authored-by: Alexey Kukanov <[email protected]>
There was a problem hiding this comment.
Below are some formatting comments, after inspecting the rendered HTML page.
Also, to me it seems excessive to italicize every occurrence of the new terms. In principle, it's enough to do once when the term is introduced; see https://oneapi-spec.uxlfoundation.org/specifications/oneapi/v1.4-rev-1/elements/onedpl/source/parallel_api/buffer_wrappers as an example for buffer position objects. I think it is OK to highlight it sometimes again, when the term is sort of reintroduced (perhaps with a link to the original definition).
Co-authored-by: Alexey Kukanov <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
| template <typename T> | ||
| inline constexpr bool is_indirectly_device_accessible_v = is_indirectly_device_accessible<T>::value; | ||
|
|
||
| ``template <typename T> oneapi::dpl::is_indirectly_device_accessible`` is a type which has the base characteristic |
There was a problem hiding this comment.
I would suggest to use "class template" or just "template" instead of type, because is_indirectly_device_accessible is not a "type"
Specification for "indirectly device accessible iterator" customization point and public trait. Based upon proposed [RFC].(uxlfoundation/oneDPL#1999)