[Development] Proposal: Deprecate QVector in Qt 6

André Pönitz apoenitz at t-online.de
Thu Apr 23 12:02:19 CEST 2020

On Thu, Apr 23, 2020 at 10:52:07AM +0200, Daniel Engelke wrote:
>    I don't see a lot of work in string replacing QList with QVector and
>    QStringList with whatever it would be, as long as the API is
>    compatible.

A proper replacing is not done by replacing one type by another.

You'd need also adapt some variable and function names,
comments and documentation are silently broken.

There's also serialization to be considered, changes to log messages,
external tools operating on stringified type names, etc.

This is a significant amount of work for non-trivial applications,
replacing the type name scratches only the surface.

>    It's even less work if auto has been used.

Not really. 'auto' saves at best the first mechanical bit concerning
the type itself.  Variables, comments etc. will not be done that way 
and will require manual interaction. It's very likely that this
work can not be done in a lot of cases, and application will simply
decide to stick to Qt 5.

I am *really* happy that this proposal came up.


More information about the Development mailing list