Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
frederick-vs-ja opened this issue Apr 4, 2021 · 2 comments
Closed

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

frederick-vs-ja opened this issue Apr 4, 2021 · 2 comments

Comments

@frederick-vs-ja
Copy link
Contributor

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
Copy link
Member

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

@frederick-vs-ja
Copy link
Contributor Author

Fixed by #4695.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@frederick-vs-ja @jensmaurer