-
Notifications
You must be signed in to change notification settings - Fork 804
[template.bitset.general][vector.bool.pspc] Make subclauses for reference nested classes
#8661
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
base: main
Are you sure you want to change the base?
[template.bitset.general][vector.bool.pspc] Make subclauses for reference nested classes
#8661
Conversation
jensmaurer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, I like this.
|
Can you make this two commits please (keep them in this single pull request)? |
2f838c5 to
afa9ade
Compare
|
Split into two commits, making the requested change to separate out the template-head in each case. |
afa9ade to
a138504
Compare
|
The commit descriptions (in particular the titles) aren't stellar. "Break out into its own subclause" is missing "reference" and/or "nested class" somewhere. In particular since the new label is [vector.bool.reference], not the quoted label. |
|
It looks like my git command line mangled my attempts to put the class names into the commit title line. I will fix just those commit messages and resubmit. |
…subclause This change is consistent with specification of nested classes elsewhere in the standard, and allows better use of qualified names in the declaration of member functions in their own specification.
…ubclause This change is consistent with specification of nested classes elsewhere in the standard, and allows better use of qualified names in the declaration of member functions in their own specification.
a138504 to
c9a4561
Compare
Consistent with other nested classes within the standard library. This formulation leads to slightly clearer specification for the member functions that now use appropriately qualified names.