Hi, Il 22/11/19 11:01, Friedemann Kleint ha scritto:
at https://wiki.qt.io/Qt_Contributors_Summit_2019_Qt_6_Changes_/_Migration
I think a clarification is in order: many of the things listed in those notes have also been discussed in other ad-hoc sessions (QtCore, QMetaType, etc.), and the resolutions in those sessions do not match what's listed in these notes.
Most notably: * QList=QVector impact is yet to be evaluated in big codebases* QString/QStringView/QLatin1String/u"" has no resultion, or better, it was agreed that has YET to be discussed * QAny was proposed and rejected, instead the idea was to fix QVariant itself somehow * returning std::optional for toInt() is just plain *wrong* and thus won't be done that way; it's at a minimum an expected type and really something even more complex (à la std::from_chars); and anyhow "how to port" is still a question
My 2 c, -- Giuseppe D'Angelo | [email protected] | 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 [email protected] https://lists.qt-project.org/listinfo/development
