Skip to content

Conversation

@eisenwave
Copy link
Member

@eisenwave eisenwave commented Feb 19, 2025

Fixes #7663.
Fixes cplusplus/papers#1993.

New Wording

image

Paper Wording

image

@jwakely
Copy link
Member

jwakely commented Feb 19, 2025

I think there should be an index entry.

@eisenwave
Copy link
Member Author

I think there should be an index entry.

An index entry for what specifically? monostate already has index entries for the class, comparison operators, and the hash specialization. These are found in [variant.monostate] etc.

Do you mean that there should be redundant index entries that also point to these declarations in [utility.syn]? Do we normally index the synopsis instead of the place of definition?

@jwakely
Copy link
Member

jwakely commented Feb 19, 2025

We don't, but it's not redundant here because it is a new occurrence of the name in a different place.

If the class is declared in two different places, I would expect two index entries.

@eisenwave eisenwave force-pushed the motions-2025-02-lwg-4 branch from 563a74d to 67e5510 Compare February 19, 2025 13:41
@tkoeppe
Copy link
Contributor

tkoeppe commented Mar 15, 2025

Please make your pull request branches writable in the future :-)

@tkoeppe tkoeppe closed this Mar 15, 2025
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.

[2025-02 LWG Motion 4] P0472R3 Put std::monostate in ⟨utility⟩ P0472 R3 Put std::monostate in <utility>

3 participants