On Tuesday 10 February 2015 19:07:09 Matthew Woehlke wrote: > Heh. That reminds me, when will Qt classes get emplace methods?
I added those methods to my local refactor of QVector, but.. > Or the ability to accept movable-but-not-copyable types? ... they aren't useful because we'll never accept movable-but-not-copyable objects. An implicitly shared container implies a copyable contained object. > (Something else to consider for Qt 6 would be fixing the index types to > be size_t instead of int. Assuming we don't just drop the classes.) For QVector, we might have to switch to qint64 or to qintptr or some other name for a *signed* integer type. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
