On Sunday 16 October 2011 16:21:40 Thiago Macieira wrote: [...] > Option 3: make it QList<T> be an actual QVector<T> for movable types, maybe > with an upper limit of size (32 bytes, 128 bytes?). > - pros: suitable for all types, shares code > - cons: more complex to implement, more code to compile and parse in > headers
This is the obvious solutions... > One big difference between QList and QVector today is that QList has prepend > / takeFirst optimisation, whereas QVector must move all elements to > accommodate. I would prefer if that optimisation remained present. It has to (it enable QList to be used for queue like data structure (and it is, see QQueue) QList was also supposed to expands to less code (than QVector) (at least that is what Jasmin used to advertise some years ago) _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
