Skip to content

[expected.object.cons] Reorder arguments of is_same_v for consistency #7915

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

Merged
merged 1 commit into from
Jun 13, 2025

Conversation

Dani-Hub
Copy link
Member

During the discussion of LWG 4222 it was noticed that [expected.object.cons] bullet (23.2) uses an atypical order of the is_same_v arguments, especially since this issue adds another bullet. To enforce consistency, the remove_cvref_t<U> argument is no also used as first (instead of second) argument in that bullet.

During the discussion of LWG 4222 it was noticed that [expected.object.cons] bullet (23.2) uses an atypical order of the is_same_v arguments, especially since this issue adds another bullet. To enforce consistency, the `remove_cvref_t<U>` argument is no also used as first (instead of second) argument in that bullet.
@Dani-Hub
Copy link
Member Author

The suggestion on the LWG reflector was to submit this as editorial issue to harmonize the suggested proposed wording for LWG 4222.

@jensmaurer
Copy link
Member

Looks obviously harmless.

@jensmaurer jensmaurer merged commit 660ab84 into cplusplus:main Jun 13, 2025
0 of 2 checks passed
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.

2 participants