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

inconsistent invalidation rules for the pointers to container elements #1651

Open
cubbimew opened this issue Jul 5, 2017 · 2 comments
Open

inconsistent invalidation rules for the pointers to container elements #1651

cubbimew opened this issue Jul 5, 2017 · 2 comments
Labels
lwg Issue must be reviewed by LWG.

Comments

@cubbimew
Copy link
Contributor

cubbimew commented Jul 5, 2017

Some paragraphs in the containers library section specify invalidation of iterators, pointers, and references, while others specify invalidation of iterators and references and make no mention of pointers.

Examples:
[deque.capacity]/8 "invalidates all the references, pointers, and iterators referring to the elements in the sequence"
[deque.modifiers]/1 "invalidates all the iterators and references to elements of the deque"

While the intent is obvious, would it be better to use the same wording everywhere, and which way should it be changed?
@zygoloid zygoloid added the lwg Issue must be reviewed by LWG. label Jul 15, 2017
@cubbimew
Copy link
Contributor Author

Shall I raise an lwg issue?

@jwakely
Copy link
Member

jwakely commented Feb 21, 2018

Yes I think that's the best place to handle it. I agree the different wording isn't meant to imply any difference in semantics, but it should probably go through LWG anyway.

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

No branches or pull requests
3 participants
@zygoloid @jwakely @cubbimew