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.

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

qualifies indirectly-readable-impl's use of iter_move #3532

Merged
merged 1 commit into from Dec 10, 2019
Merged

qualifies indirectly-readable-impl's use of iter_move #3532

merged 1 commit into from Dec 10, 2019

Conversation

cjdb
Copy link
Contributor

@cjdb cjdb commented Dec 9, 2019

The exposition-only concept indirectly-readable-impl relies on
ranges::iter_move, but the text was missing the ranges:: qualifier.
This commit adds it, as the intention is to use ranges::iter_move, not
std::iter_move.

cc @jwakely @CaseyCarter @ericniebler @timsong-cpp

@jwakely
Copy link
Member

jwakely commented Dec 9, 2019

Thanks, Chris. Please add the stable tag [iterator.concept.readable] to the start of your commit message (and re-push).

…of iter_move

The exposition-only concept _`indirectly-readable-impl`_ relies on
`ranges::iter_move`, but the text was missing the `ranges::` qualifier.
This commit adds it, as the intention is to use `ranges::iter_move`, not
`std::iter_move`.
@CaseyCarter
Copy link
Contributor

I find it incredibly ironic that the commit message doesn't say "...use of ranges::iter_move" (No change requested) =)

@jensmaurer jensmaurer merged commit 4dd1859 into cplusplus:master Dec 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants