---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115739/#review51000
---
This review has been submitted with commit
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115739/
---
(Updated Feb. 27, 2014, 7:52 a.m.)
Status
--
This change has been
On Feb. 15, 2014, 8:28 p.m., David Faure wrote:
Yeah the description is wrong. Making something Q_MOVABLE means that
inserting into the list, or the copying that happens when reallocating for
more space, will be able to memmove() instead of copy-constructing items.
This doesn't
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115739/#review50566
---
Ship it!
Thanks!
tests/listjobtest.cpp
On Feb. 15, 2014, 8:28 p.m., David Faure wrote:
Yeah the description is wrong. Making something Q_MOVABLE means that
inserting into the list, or the copying that happens when reallocating for
more space, will be able to memmove() instead of copy-constructing items.
This doesn't
On Feb. 13, 2014, 9:31 p.m., Christoph Feck wrote:
Making the type movable does not make QList store it directly, how did you
check this?
http://qt-project.org/doc/qt-5/qlist.html says:
Internally, QListT is represented as an array of pointers to items of
type T. If T is
On Feb. 13, 2014, 9:31 p.m., Christoph Feck wrote:
Making the type movable does not make QList store it directly, how did you
check this?
http://qt-project.org/doc/qt-5/qlist.html says:
Internally, QListT is represented as an array of pointers to items of
type T. If T is
