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.

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

[temp] p1 what is a family of classes? and can they claim dependents? ;) #1787

Closed
faisalv opened this issue Oct 27, 2017 · 2 comments
Closed

[temp] p1 what is a family of classes? and can they claim dependents? ;) #1787

faisalv opened this issue Oct 27, 2017 · 2 comments

Comments

@faisalv
Copy link
Contributor

faisalv commented Oct 27, 2017

Why not eschew the non-technical term 'family' and deviate from the ARM in favor of something more descriptive along the lines of:
A template defines a pattern (borrowing from [temp.variadic]) for generating/instantiating an unbounded set of related classes ... etc.

not better?
@jensmaurer
Copy link
Member

We should be aware that we're talking about a warm-up introductory sentence that just happens not to be in a note. I'd like to get a consensus on the general approach here first (see #1771) before addressing specific issues.

As a side note, I dislike "unbounded": There are templates that can only be instantiated with a single type (think static_assert(is_same_v<T, int>)). Also, "related": what's the relationship between two classes instantiated from the same template? These are distinct classes, after all.

So, something like "A template defines a pattern for a set of classes, functions, or variables, an alias for a set of types, or a concept." sounds workable.

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 1, 2017
@jensmaurer
Copy link
Member

Editorial meeting consensus: Disrupting this wording in the proposed way is no match for the conceivable fall-out. No consensus for a change.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 7, 2017
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
@faisalv @jensmaurer