On 4/24/20 8:57 AM, Joerg Bornemann wrote:
Alternatively, proposal 3 (aka "do almost nothing"):
template <typename T> class QVector { implementation }
template <typename T> using QList = QVector<T>;
No deprecation of QVector.
No replacement of QList with QVector in our API.
Rationale: QList is our default sequential container, and in Qt6 we just
change its implementation.
Could you please argument a bit more? In particular:* Is it OK to live with a mixup of containers in the APIs? What's the downside in terms of consistency, teachability, learning, etc.?
* If I'm adding a new function, what would the coding guideline be, take/return QList or QVector? Why?
* What's the reason against the replacement? It's not worth it in terms of manpower, or another guideline?
Thanks, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
