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

GB280 24.04.2 Rename forwarding-range to avoid near-clash with forward_range P1870 #276

Closed
wg21bot opened this issue Oct 24, 2019 · 5 comments · Fixed by cplusplus/draft#3486
Labels
accepted LEWG Library Evolution ranges std::ranges
Milestone

Comments

@wg21bot
Copy link
Collaborator

wg21bot commented Oct 24, 2019

forwarding-range is too-easily confused with forward_range

Proposed change:
Please find an alternative name for forwarding-range, as it is extremely similar to forward_range, which is (a) different in definition, and (b) a user-facing concept.

@wg21bot wg21bot added the LEWG Library Evolution label Oct 24, 2019
@jensmaurer jensmaurer added the ranges std::ranges label Oct 25, 2019
@zygoloid
Copy link
Member

Renaming the exposition-only concept is editorial, if LEWG can find a preferable alternative name.

@brevzin
Copy link
Collaborator

brevzin commented Oct 31, 2019

See also US279 #275.

@tituswinters
Copy link

Resolved by #275

@jensmaurer jensmaurer changed the title GB280 24.04.2 Rename forwarding-range to avoid near-clash with forward_range GB280 24.04.2 Rename forwarding-range to avoid near-clash with forward_range P1870 Nov 8, 2019
@jensmaurer
Copy link
Member

Accepted.

@jensmaurer
Copy link
Member

See P1870 cplusplus/papers#620

@jensmaurer jensmaurer added this to the CD C++20 milestone Sep 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted LEWG Library Evolution ranges std::ranges
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants