[iterator.cust.swap] Should iter_move be qualified with ranges::?

[frederick-vs-ja]

It is clear that iter_move in [iterator.cust.swap] denotes ::std::ranges::iter_move. However, it seems that [contents]/3 makes unqualified iter_move denote the non-existing ::std::iter_move.

So should we qualify these occurrences of iter_move with ranges::?

[jensmaurer]

A change here is not desirable. This should be addressed by #1913.

[frederick-vs-ja]

Fixed by #4695.