Skip to content

[indirect.general, polymorphic.general] Should we define "indirect/polymorphic object"? #7885

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

Open
frederick-vs-ja opened this issue May 21, 2025 · 1 comment

Comments

@frederick-vs-ja
Copy link
Contributor

Currently, "indirect object" and "polymorphic object" are not formally introduced by italic style texts. Should we define them as "object whose type is an indirect/polymorphic specialization"?

On the other hand, as a "polymorphic object" mentioned [polymorphic.general] isn't an object of a polymorphic class type, and isn't even required to manage polymorphic class objects. Should we use another phrase or "polymorphic object" to avoid ambiguity?

@jwakely
Copy link
Member

jwakely commented May 21, 2025

We do introduce optional object but not as formally as "an object whose type is a specialization of optional". Elsewhere we don't even bother with that, e.g. "A variant object holds and manages the lifetime of a value."

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

No branches or pull requests

2 participants