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.

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

Avoid ambiguity between "size of" and "sizeof" in [string.capacity] max_size() #255

Closed
jyasskin opened this issue Dec 28, 2013 · 0 comments · Fixed by #994
Closed

Avoid ambiguity between "size of" and "sizeof" in [string.capacity] max_size() #255

jyasskin opened this issue Dec 28, 2013 · 0 comments · Fixed by #994

Comments

@jyasskin
Copy link
Contributor

Regarding, [string.capacity], Alisdair points out that "'size of' may also refer to the result of the 'sizeof' operator, so I would use 'length' instead, as we define both."

Daniel then points out:
"I think that using the notion of "length" still makes the meaning unclear, it is now like a recursive definition, because length() is defined in terms of size(), not vice versa. What about:

"The largest possible number of char-like objects that can be [stored in] a [basic_string]."

(I edited the above to adapt their suggestions from basic_string_view to basic_string.)

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

Successfully merging a pull request may close this issue.

1 participant