Comments on: Moving Ranges Around with STL Algorithms

By: Edoardo Morandi

Edoardo Morandi — Sun, 22 Apr 2018 14:57:00 +0000

In reply to Jonathan Boccara. Yes, I was talking about the `std::swap` because it is the prerequisite for many algorithms. In my projects I am already using many constexpr functions ported from std (including `swap`), but is an awful copy-and-paste work from stdlib. I was hoping to have much more constexpr things in c++20, but at this point I am a bit hopeless...

By: Jonathan Boccara

Jonathan Boccara — Sat, 21 Apr 2018 21:58:00 +0000

In reply to Edoardo Morandi. Hi Edoardo, I don't think that's an error in the wiki as some STL algorithms, such as std::sort also, shouldn't be constexpr in C++20.

By: Ole Erik Peistorpet

Ole Erik Peistorpet — Tue, 17 Apr 2018 16:54:00 +0000

Remember that back() is the last element in a range (with greatest index). As such, the names copy_backward and move_backward are consistent with that.

By: Edoardo Morandi

Edoardo Morandi — Tue, 17 Apr 2018 07:26:00 +0000

Inside cppreference.com I noticed that neither `std::swap` or `std::swap_range` are marked constexpr with C++20. Is it a defect of the wiki or there are some troubles constexpr-ing these two functions for the next standard?

By: Davidbrcz

Davidbrcz — Fri, 13 Apr 2018 07:20:00 +0000

I think it was Sean Parent in one of his talks who showed that shift_right and shift_left can already be implemented in term of std::rotate