On Tuesday, 4 December 2018 08:28:13 PST Adam Light wrote: > Another place where this can be a problem is QMimeData, which uses a > QByteArray. We'd like for our application to be able to read/write >2GB > from/to the clipboard, but that's not currently possible. Reimplementing > all clipboard handling ourselves on two platforms would be a lot of work > and using std:: containers with Qt's clipboard API isn't an option.
Right. My point is that even if we didn't want to make the effort to apply it for most containers, we'd need to do it in QString and QByteArray. Those two share most of their internals with QVector, so doing it for QVector (especially after my changes from Qt 5.0 still unpushed) should be acceptable. Then QList will become QVector in Qt 6, so that gets done too. QHash and QMap will probably be rewritten, so they're backed by std::unordered_map, so it's a good time to do it too. That just leaves QLinkedList. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
