On Tuesday 19 January 2016 17:00:35 Thiago Macieira wrote: > On Tuesday 19 January 2016 15:07:58 Marc Mutz wrote: > > It may, yes. With the current speed of Qt container development, though, > > I don't see this coming to fruition. > > The current speed of development is limited by the availability of major > releases.
It's laudable that you're doing work on the containers, however I don't share that sentiment. > Most of what I want to do cannot be done until Qt 6. That may be so. But most of what is _missing_ is implementable in Qt 5: - equal_range on hashed containers - range inserts, ctors, assignments - exception safety guarantees - move semantics on realloc / insertions - emplace (with Q_COMPILER_UNIFORM_INIT ifdef) - not requiring op= / default ctor in QVector - move-only payload types (hard with CoW) - splicing in node-based containers (hard with CoW) - atomic operations on QSharedPointer - alias ctors for QSharedPointer - changing iterator → const_iterator in insert / erase arguments (hampered by QT_STRICT_ITERATORS preventing iterator → const_iterator implicit conversions, otherwise one could write erase loops over node-based containers that only detach when actually removing an element) - ... Thanks, Marc -- Marc Mutz <marc.m...@kdab.com> | Senior Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company Tel: +49-30-521325470 KDAB - The Qt Experts _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
