|  | Commit message (Collapse) | Author | Age | Files | Lines | 
|---|
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | Summary: The keys must still be copyable, because we store two copies of them.
Reviewers: timshen
Subscribers: llvm-commits
Differential Revision: https://reviews.llvm.org/D25404
llvm-svn: 283764 | 
| | 
| 
| 
| 
| 
| | a subsequent commit in Clang.
llvm-svn: 233159 | 
| | 
| 
| 
| 
| 
| | and a Vector of SmallVector.
llvm-svn: 225054 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| | MapVector::begin(), MapVector::end().
These just delegate to the underlying vector type in the MapVector.
Also just add in some sanity unittests.
llvm-svn: 220687 | 
| | 
| 
| 
| | llvm-svn: 219250 | 
| | 
| 
| 
| | llvm-svn: 219240 | 
| | 
| 
| 
| 
| 
| 
| | Add a `MapVector::remove_if()` that erases items in bulk in linear time,
as opposed to quadratic time for repeated calls to `MapVector::erase()`.
llvm-svn: 213090 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | Actually update the changed indexes in the map portion of `MapVector`
when erasing from the middle.  Add a unit test that checks for this.
Note that `MapVector::erase()` is a linear time operation (it was and
still is).  I'll commit a new method in a moment called
`MapVector::remove_if()` that deletes multiple entries in linear time,
which should be slightly less painful.
llvm-svn: 213084 | 
| | 
| 
| 
| 
| 
| | unit test.
llvm-svn: 175538 | 
|  | llvm-svn: 173505 |