Hi Simon, I hope it's not a belated April's Fool joke? As far as I can remember, for the past few years, one would read everywhere to switch to QVector from QList because of this and that, and to choose QVector as the default choice container instead of QList like it was back in the days. I can't give the exact references but that's just the feeling I get from reading the docs and the Qt mailing lists.
Cheers Dmitriy On Thu, Apr 23, 2020 at 9:45 AM Simon Hausmann <simon.hausm...@qt.io> wrote: > Hi, > > In dev we've had QVector being an alias for QList for a while now. For the > 6.0 release this particular topic (QList/QVector) suggests two goals (among > others): > > (1) Use the same type throughout the public API of Qt. > > (2) Make it easy for our users to maintain a code base that works with > Qt 5 and 6. > > > In the light of those two goals, I think we should keep using QList as the > type in the public API. I don't think we should do a search and replace > activity and switch to QVector. In the light of that, I would like to > propose simply deprecating QVector and stick to QList everywhere. > > > What do you think? > > > Simon > _______________________________________________ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development >
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
