| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. I had been detecting and trapping iterator == and \!= among iterators
in different containers as an error. But the trapping itself is actually
an error.
Consider:
#include <iostream>
#include <vector>
#include <algorithm>
template <class C>
void
display(const C& c)
{
std::cout << "{";
bool first = true;
for (const auto& x : c)
{
if (\!first)
std::cout << ", ";
first = false;
std::cout << x;
}
std::cout << "}\n";
}
int
main()
{
typedef std::vector<int> V;
V v1 = {1, 3, 5};
V v2 = {2, 4, 6};
display(v1);
display(v2);
V::iterator i = std::find(v1.begin(), v1.end(), 1);
V::iterator j = std::find(v2.begin(), v2.end(), 2);
if (*i == *j)
i = j; // perfectly legal
// ...
if (i \!= j) // the only way to check
v2.push_back(*i);
display(v1);
display(v2);
}
It is legal to assign an iterator from one container to another of the
same type. This is required to work. One might want to test whether or
not such an assignment had been made. The way one performs such a check
is using the iterator's ==, \!= operator. This is a logical and necessary
function and does not constitute an error.
2. I had a header circular dependence bug when _LIBCPP_DEBUG2 is defined.
This caused a problem in several of the libc++ tests.
Fixed.
3. There is a serious problem when _LIBCPP_DEBUG2=1 at the moment in that
std::basic_string is inoperable. std::basic_string uses __wrap_iterator
to implement its iterators. __wrap_iterator has been rigged up in debug
mode to support vector. But string hasn't been rigged up yet. This means
that one gets false positives when using std::string in debug mode. I've
upped std::string's priority in www/debug_mode.html.
llvm-svn: 187636
|
| |
|
|
| |
llvm-svn: 184859
|
| |
|
|
| |
llvm-svn: 184691
|
| |
|
|
| |
llvm-svn: 178892
|
| |
|
|
| |
llvm-svn: 178819
|
| |
|
|
|
|
| |
two flags: _LIBCPP_TYPE_VIS and _LIBCPP_FUNC_VIS. This is in preparation for taking advantage of clang's new __type_visibility__ attribute.
llvm-svn: 176593
|
| |
|
|
|
|
| |
send me a patch to CREDITS.TXT?
llvm-svn: 163862
|
| |
|
|
| |
llvm-svn: 145410
|
| |
|
|
| |
llvm-svn: 145407
|
| |
|
|
| |
llvm-svn: 142235
|
| |
|
|
|
|
| |
should be considered a temporary state. The API of the debug database and how vector and list use it, is unsatisfactory at the moment. It is both inefficient and overly verbose. I wanted to get this functionality checked in though. In the next day or so I'll refactor what is there in an attempt to streamline things.
llvm-svn: 140660
|
| |
|
|
| |
llvm-svn: 139032
|
| |
|
|
| |
llvm-svn: 137522
|
| |
|
|
| |
llvm-svn: 134190
|
| |
|
|
|
|
| |
The purpose is to aid automated documentation tools.
llvm-svn: 133008
|
| |
|
|
| |
llvm-svn: 132562
|
| |
|
|
|
|
| |
qualified (thanks Chris).
llvm-svn: 125510
|
| |
|
|
| |
llvm-svn: 124726
|
| |
|
|
| |
llvm-svn: 124508
|
| |
|
|
| |
llvm-svn: 119395
|
| |
|
|
| |
llvm-svn: 114551
|
| |
|
|
|
|
| |
flags, and renamed _LIBCPP_MOVE to _LIBCPP_HAS_NO_RVALUE_REFERENCES to be more consistent with the rest of the libc++'s flags, and with clang's nomenclature.
llvm-svn: 113086
|
| |
|
|
| |
llvm-svn: 111750
|
| |
|
|
| |
llvm-svn: 103516
|
|
|
llvm-svn: 103490
|
