boostorg / boostorg/compute

is_contiguous_iterator should be a public customization point

Open
#402 3 comments 0 reactions 0 assignees View on GitHub
design feature
Dominant language
C++
Stars
1.7k
Forks
340
PR merge metrics
No merged PRs in 30d

Description

Currently the library specializes is_contiguous_iterator for containers it knows to have contiguous iterators. However, it seems likely that users will have their own vector-like containers (indeed, there are several in Boost already). It would be helpful if is_contiguous_iterator was a documented customization point by which users could mark their own iterators as contiguous.

(Indeed, the library already misses one standard one: std::string::iterator)
##

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.