| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
horrible smart pointer by std::unique_ptr and strict move semantics, rip
this out.
llvm-svn: 203392
|
|
|
|
|
|
| |
directly, and remove the macro.
llvm-svn: 202612
|
|
|
|
| |
llvm-svn: 202583
|
|
|
|
|
|
|
|
| |
This bug only bit the C++98 build bots because all of the actual uses
really do move. ;] But not *quite* ready to do the whole C++11 switch
yet, so clean it up. Also add a unit test that catches this immediately.
llvm-svn: 194548
|
|
|
|
|
|
| |
a derived type and this makes it *much* easier to write this code.
llvm-svn: 194321
|
|
|
|
| |
llvm-svn: 194320
|
|
|
|
|
|
|
|
|
| |
r-value references. I still want to test that when we have them,
llvm_move is actually a move.
Have I mentioned that I really want to move to C++11? ;]
llvm-svn: 194318
|
|
|
|
|
|
|
|
|
|
| |
Clang managed to never instantiate the copy constructor. Added tests to
ensure this path is tested.
We could still use tests for the polymorphic nature. Those coming up
next.
llvm-svn: 194317
|
|
|
|
|
|
| |
to fix C++98 builds.
llvm-svn: 194316
|
|
unique ownership smart pointer which is *deep* copyable by assuming it
can call a T::clone() method to allocate a copy of the owned data.
This is mostly useful with containers or other collections of uniquely
owned data in C++98 where they *might* copy. With C++11 we can likely
remove this in favor of move-only types and containers wrapped around
those types.
llvm-svn: 194315
|