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

[strings] Use "Equivalent to" where appropriate #165

Closed
sdutoit opened this issue Aug 28, 2013 · 4 comments
Closed

[strings] Use "Equivalent to" where appropriate #165

sdutoit opened this issue Aug 28, 2013 · 4 comments
Labels
lwg Issue must be reviewed by LWG.

Comments

@sdutoit
Copy link
Contributor

sdutoit commented Aug 28, 2013

From an email by Jeffrey Yasskin:

Many functions in the strings clause use formulations like:

[string.cons]/15:

Effects: Same as basic_string(il.begin(), il.end(), a).

[string.capacity]/15:

Effects: Behaves as if the function calls:
erase(begin(), end());

[string::insert]/27:

Effects: insert(p, il.begin(), il.end()).
Returns: [what the above insert() call returns]

instead of the "Equivalent to" wording defined in
[structure.specifications]/4. These should all be changed to
"Equivalent to" for consistency and conciseness.

@burblebee
Copy link
Contributor

This needs to be opened as an LWG issue. I've asked for an issue to be opened for this throughout the spec, but I don't know it's number yet.

@burblebee burblebee added the lwg Issue must be reviewed by LWG. label Apr 15, 2016
@jensmaurer
Copy link
Member

jensmaurer commented Dec 9, 2016

LWG 2679, but that doesn't cover the places mentioned above.

@jensmaurer
Copy link
Member

I've asked for another LWG issue, explicitly listing the places that need fixing.

@jensmaurer
Copy link
Member

LWG 2841

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lwg Issue must be reviewed by LWG.
Projects
None yet
Development

No branches or pull requests

3 participants