Skip to content

[derivation] Do we need to clarify "all types specified in the C++ standard library"? #7858

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.

Sign up for GitHub

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

Jump to bottom
Open
frederick-vs-ja opened this issue Apr 27, 2025 · 1 comment
Open

[derivation] Do we need to clarify "all types specified in the C++ standard library"? #7858

frederick-vs-ja opened this issue Apr 27, 2025 · 1 comment

Comments

@frederick-vs-ja
Copy link
Contributor

Does [derivation]/4 (added via LWG2514) cover only standard library classes (and possibly some internal exposition-only classes whose synopses are specified), or ever more classes (observable by the user code) provided by the implementation?

E.g. are some implementation-defined or unspecified iterator types, or return types or std::bind etc. allowed to be final?
@jwakely
Copy link
Member

jwakely commented Apr 27, 2025

Everything about unspecified types that isn't stated explicitly is unspecified, including whether they're final. We don't need to say anything for them, because unspecified types are not covered by that paragraph. For exposition-only types where we do specify a class definition, we might want to clarify whether those can or can't be final.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jwakely @frederick-vs-ja