Marc, I think you misunderstand the nature of the discussion. I don't think anyone disputes your analysis of the relative efficiencies of the various collections. I think you are dismissing the simple elegance of QList for getting a Qt application up and running quickly. Or, as in my use case, making a change quickly to correct a bug.
I can see by your explanation that QVector is almost always more efficient than QList. But sometimes the difference doesn't matter. martin ________________________________________ From: development-bounces+martin.smith=theqtcompany....@qt-project.org <development-bounces+martin.smith=theqtcompany....@qt-project.org> on behalf of Marc Mutz <marc.m...@kdab.com> Sent: Sunday, July 12, 2015 7:14 PM To: development@qt-project.org Subject: Re: [Development] Container benchmark was HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO On Sunday 12 July 2015 17:34:25 Smith Martin wrote: > I like QList. This level of discussion, combined with a complete unwillingness to look anything up that was linked to in this thread is why I don't try patch the Qt docs. And I'm sorry for not having stuck to my initial resolve not to talk about _why_ QList is bad. All the information is out there, and I won't convince anyone who's TL;DR; Hereby reinstated. -- Marc Mutz <marc.m...@kdab.com> | Senior Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company Tel: +49-30-521325470 KDAB - The Qt Experts _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
