20 Aug
2014
20 Aug
'14
12:26 p.m.
On 19/08/14 18:49, John Maddock wrote:
The intent was always to submit is_iterator to Boost, but we never got around to it. Now I need it in Boost.Filesystem, so I'd rather see it go in type traits than just sticking it into boost/filesystem/detail.
Out of curiosity, why do you need it?
One situation is inside a constructor call:
struct myclass { template <class I> myclass(I a, I b) { // a and b could be iterators, or could be a pair of values, // we need to separate the two cases. }
What if your values are iterators?