Welcome to container hell, please take a seat

You might also have a look at _Assign_range

Could someone explain to me why move_iterator's iterator_concept is input_iterator_tag?

Also counts towards #189

Could someone explain to me why move_iterator's iterator_concept is input_iterator_tag?

I believe this is because a Forward Iterator can be read multiple times (the idea is that they're like forward_list - they support only forward traversal, but otherwise point to persistent objects in memory). Input Iterators can be read only once (like an istream_iterator, you can't store multiple "locations" to read previous values). move_iterator is weird because although it can wrap something with very strong traversal (up to and including random access), the automatic-moving breaks multi-read behavior. Thus, describing move_iterator with input_iterator_tag is the strictly correct thing to do.

Apologies for the year-long delay in answering this question 😹

@StephanTLavavej It seems that it might change with P2520.

Thanks, this looks great! I found only minor issues while video reviewing, so I went ahead and validated and pushed changes.

I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed.

Thanks for improving the performance of the STL's most important data structure! 😻 🚀 🚀

Youtube Link to the Code Review of this PR