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
From my understanding (by reading the Boost.Iterator docs) iterator traversal is distinct from element access, so a proxy iterator (not returning a T&) can also be declared to be random access. E.g. a counting iterator is a input_iterator, because its value type is not a reference. However, this concept is obsolete in C++20, where iterator tags were replaced in favor of iterator concepts.
We should move any thrust iterator traversal trait into a detail namespace and add deprecated public aliases. Users should move away from this functionality.
We should replace iterator traversal by the C++20 iterator concepts in the long run.
The text was updated successfully, but these errors were encountered:
bernhardmgruber
changed the title
Move any thrust iterator traversal trait into a detail namespace and add deprecated public aliases
Deprecate thrust iterator traversal
Jan 28, 2025
From my understanding (by reading the Boost.Iterator docs) iterator traversal is distinct from element access, so a proxy iterator (not returning a T&) can also be declared to be random access. E.g. a counting iterator is a input_iterator, because its value type is not a reference. However, this concept is obsolete in C++20, where iterator tags were replaced in favor of iterator concepts.
We should move any thrust iterator traversal trait into a detail namespace and add deprecated public aliases. Users should move away from this functionality.
We should replace iterator traversal by the C++20 iterator concepts in the long run.
The text was updated successfully, but these errors were encountered: