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
(bunch of ranges) inconsistency about whether *_view::iterator
has the class
or struct
class-key
#5901
Comments
strega-nil-ms
changed the title
(bunch of ranges) inconsistency about whether _
(bunch of ranges) inconsistency about whether <i><code>*_view::iterator</code></i> has the Oct 11, 2022
*_view::iterator
_ has the class
or struct
_class-key_class
or struct
_class-key_
strega-nil-ms
changed the title
(bunch of ranges) inconsistency about whether <i><code>*_view::iterator</code></i> has the
(bunch of ranges) inconsistency about whether Oct 11, 2022
class
or struct
_class-key_*_view::iterator
has the class
or struct
_class-key_
strega-nil-ms
changed the title
(bunch of ranges) inconsistency about whether
(bunch of ranges) inconsistency about whether Oct 11, 2022
*_view::iterator
has the class
or struct
_class-key_*_view::iterator
has the class
or struct
class-key
See #5323. |
there is also the inconsistency between ranges, but I think the inconsistency for a specific range is ... well, it's more annoying anyways, given that it's ill-formed. |
It's not ill-formed |
huh. today I learned, I thought it was, but it's just the MSVC name decoration that changes. |
Which is an infamous msvc conformance bug. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example, in [range.repeat.view], the
repeat_view::iterator
member class is declared with the class-keystruct
. However, in [range.repeat.iterator],repeat_view::iterator
is declared with the class-keyclass
.This is also true for:
The class-keys are consistently
struct
for:The others all use class-key
class
.The text was updated successfully, but these errors were encountered: