Il 24/05/19 14:09, Mutz, Marc via Development ha scritto:
2. Keep QList as-is. It cannot be an alias to QVector/QArrayList, nor can it be implemented in terms of either (only at the d-pointer level)Is it worth the cost? I don't know.
I'm still in favour at keeping QList as-is and paying the conversion price. We're talking about code that users should _stop_ using anyhow, and port away from it, right? I.e. Q5List in Qt 6.0 is going to emit deprecation warnings?
(And the port away could be as simple as a s/QList/QVector/ if the codebase is not using any of the QList "fancy" features.)
My 2 c, -- 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: Firma crittografica S/MIME
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
