Skip to content

Conversation

@AlisdairM
Copy link
Contributor

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.

Copy link
Member

@jensmaurer jensmaurer left a 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.

@jensmaurer
Copy link
Member

Can you make this two commits please (keep them in this single pull request)?

@AlisdairM AlisdairM force-pushed the create_subclause_for_reference_types branch 4 times, most recently from 2f838c5 to afa9ade Compare December 22, 2025 18:08
@AlisdairM
Copy link
Contributor Author

Split into two commits, making the requested change to separate out the template-head in each case.

@AlisdairM AlisdairM requested a review from jensmaurer December 22, 2025 19:44
@AlisdairM AlisdairM force-pushed the create_subclause_for_reference_types branch from afa9ade to a138504 Compare December 22, 2025 20:58
@AlisdairM AlisdairM requested a review from jensmaurer December 22, 2025 21:03
@jensmaurer
Copy link
Member

jensmaurer commented Dec 22, 2025

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.

@AlisdairM
Copy link
Contributor Author

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.
@AlisdairM AlisdairM force-pushed the create_subclause_for_reference_types branch from a138504 to c9a4561 Compare December 22, 2025 21:36
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.

3 participants