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

[any] "contained value" vs "contained object" #1401

Closed
lynnboy opened this issue Jan 23, 2017 · 1 comment
Closed

[any] "contained value" vs "contained object" #1401

lynnboy opened this issue Jan 23, 2017 · 1 comment
Assignees
@jensmaurer

Comments

@lynnboy
Copy link

lynnboy commented Jan 23, 2017

In [optiona] and [variant], "contained value" is the term refer to the object inside, but in [any], in general it uses "contained object", but still use "contained value" at some places.
We should unify the term as "contained value".
@jensmaurer
Copy link
Member

Also, [variant] doesn't italics-define "contained value", but should, to make the index consistent.

jensmaurer added a commit to jensmaurer/draft that referenced this issue Feb 10, 2017
@jensmaurer
[any] Use 'contained value' consistently.
f182613 
This harmonizes the use of 'constained value' across
optional, variant, and any, with appropriate index
entries.

Fixes cplusplus#1401.
@jensmaurer jensmaurer mentioned this issue Feb 10, 2017
Merged
@jensmaurer jensmaurer self-assigned this Feb 10, 2017
zygoloid pushed a commit that referenced this issue Mar 2, 2017
@jensmaurer @zygoloid
[any] Use 'contained value' consistently.
bdff868 
This harmonizes the use of 'constained value' across
optional, variant, and any, with appropriate index
entries.

Fixes #1401.
@lynnboy lynnboy mentioned this issue Mar 28, 2017
Closed
@jwakely jwakely mentioned this issue Nov 8, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lynnboy @jensmaurer