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

"undefined" vs "not defined" for declared-but-not-defined primary templates #528

Closed
timsong-cpp opened this issue Jul 23, 2015 · 1 comment
Closed

"undefined" vs "not defined" for declared-but-not-defined primary templates #528

timsong-cpp opened this issue Jul 23, 2015 · 1 comment

Comments

@timsong-cpp
Copy link
Contributor

result_of uses // not defined. tuple_size, tuple_element, function and packaged_task uses // undefined. They should be made consistent.
@jensmaurer
Copy link
Member

jensmaurer commented Nov 17, 2016 •
edited

I'm opting for "not defined", since "undefined" sounds too much like "undefined behavior"... and is used as such in the core language sections.

jensmaurer added a commit to jensmaurer/draft that referenced this issue Nov 17, 2016
@jensmaurer
[utilities], [futures.task] Use 'not defined', not 'undefined', to pr…
98e4daa 
…esent library declarations of primary templates that are not supposed to have a definition.

Fixes cplusplus#528.
@jensmaurer jensmaurer mentioned this issue Nov 17, 2016
Merged
tkoeppe pushed a commit that referenced this issue Nov 17, 2016
@jensmaurer @tkoeppe
[utilities], [futures.task] Use 'not defined', not 'undefined', to pr…
c9189b9 
…esent library declarations of primary templates that are not supposed to have a definition. (#1063)

Fixes #528.
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
@timsong-cpp @jensmaurer