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

[expr.prim.lambda.closure] insert an extra pnum #6594

Merged
merged 1 commit into from Oct 9, 2023

Conversation

AlisdairM
Copy link
Contributor

Paragraph 2 does two things. The part before the note specifies the scope where the closure type is defined. The part after the note places constraints on how the closure type can be implemented. Adding a paragraph number after the note seems to be more readable, and referencable in the future.

P2 does two things.  The part before the note specifies the
scope where the closure type is defined.  The part after the
note places constraints on how the closure type can be
implemented.  Adding a paragraph number after the note
seems to be more readable, and referencable in the future.
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.

Why not.

@jensmaurer jensmaurer merged commit dc597fa into cplusplus:main Oct 9, 2023
2 checks passed
@AlisdairM AlisdairM deleted the extra_pnum_for_lambda_closure branch November 14, 2023 19:17
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

2 participants