[Bug libstdc++/126604] std::inclusive_scan moves from the first element of the input range

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D126604

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Christopher Obbard from comment #0)
> For a value type with a destructive move

std::string does not have a "destructive move", that term has a
well-established meaning that is completely different from your usage:
https://www.foonathan.net/2017/09/destructive-move/#destructive-move-the-ba=
sics=