Creating a function pointer with proper parameters pointing to std::next() or std::prev() should work.
This change moves the invented paramater for enable_if over to the return type to resolve this QoI issue.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
include/iterator | ||
---|---|---|
619 ↗ | (On Diff #104030) | Might fix the spelling error in "BidirectionalIter" while you're here. |
Comment Actions
Creating a function pointer with proper parameters pointing to std::next() or std::prev() should work.
Actually, according to the standard taking the address of a STL function is UB, and users should avoid doing it as much as possible since it's fundamentally non-portable.
However as a QoI change I think this is OK.