This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/70716] New: Doxygen comments on std containers need updating for C++11 allocators
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 18 Apr 2016 11:43:05 +0000
- Subject: [Bug libstdc++/70716] New: Doxygen comments on std containers need updating for C++11 allocators
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70716
Bug ID: 70716
Summary: Doxygen comments on std containers need updating for
C++11 allocators
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords: documentation
Severity: minor
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
We have comments on copy constructors like:
* The newly-created %deque uses a copy of the allocation object used
* by @a __x.
and copy assignment:
* All the elements of @a x are copied, but unlike the copy constructor,
* the allocator object is not copied.
These need updating, as the behaviour depends on the allocator traits now.
Also, assignment operators and functions often say "Old data may be lost." I
think that's a confusing way to say that old elements are replaced, do we
really want to talk about data loss?