diff options
| author | Giuseppe D'Angelo <giuseppe.dangelo@kdab.com> | 2013-07-27 00:58:27 +0200 |
|---|---|---|
| committer | The Qt Project <gerrit-noreply@qt-project.org> | 2013-07-28 23:09:10 +0200 |
| commit | 5b9006bbdba7dcab01b8e640554a7d7a4b64f76b (patch) | |
| tree | 9fac766b361f86514184382ac05e13be95291f5f /src/corelib/tools/qeasingcurve.cpp | |
| parent | 69b31f7b657a7ca611ad980c2974597de160598c (diff) | |
Implement move-ctor and move-assignment-op for QScopedPointer
It makes sense for a QScopedPointer to be movable, for instance
for allowing instances to be returned from a function.
Ownwership of the managed pointer is still tied to one (and one only)
QScopedPointer instance.
Moreover, a move assignment operator makes sense as well, as it
implementing the equivalent of
this->reset(other.take());
only when other is a rvalue and not a lvalue (so either it's a temporary
or it's getting explicitly moved in with std::move).
This makes QScopedPointer API's a bit closer to std::unique_ptr's one.
Task-number: QTBUG-29754
Change-Id: If1ac0c688327a67af4ad5b7ad45b439b022ed1c6
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Diffstat (limited to 'src/corelib/tools/qeasingcurve.cpp')
0 files changed, 0 insertions, 0 deletions