Closed mikezackles closed 3 years ago
Yes, it is intended behavior not to rely on std::iterator_traits, specially for compilation times. I don't know which protocol ranges-v3 follows for its iterators, but it would be a nice addition.
It seems ranges-v3 compatibility it's not a very requested feature since 2018 so I'm closing this issue. Thanks for the issue.
I was attempting to use range-v3 with
boost::container::small_vector
, but by default there is an issue with converting range-v3 iterators for use withsmall_vector::insert
. range-v3 internally specializesstd::iterator_traits
, but movelib seems to ignore this specialization.I can fix the issue with something like
but I wanted to make sure this is intended behavior.
Thanks!