[Development] Proposal: Deprecate QVector in Qt 6

Ville Voutilainen ville.voutilainen at gmail.com
Fri Apr 24 17:34:37 CEST 2020

On Fri, 24 Apr 2020 at 13:58, Edward Welbourne <edward.welbourne at qt.io> wrote:
> Giuseppe D'Angelo (24 April 2020 10:19) asked
> >>> Which "one year release approach" are we talking about here?
> On 4/24/20 12:36 PM, Edward Welbourne wrote:
> >> That would be Vitaly's proposal to have major releases yearly.
> Giuseppe D'Angelo (April 24, 2020 12:38)
> > I must be missing something: how would that help, regarding the
> > problem at hand? In other words, how does such a decision influence
> > the solution of the problem?
> Vitaly favours getting rid of QList in Qt6 and providing tools to
> automate conversion.  Some of us will only consider this a credible
> option when we see those tools in operation.  Quite how the faster major
> release cycle would bear on this, I must leave Vitaly to answer.

Unless there are conversion tools that can convert back and forth, this approach
will never work. The fairytale of automatic conversion that is usually
spun fails
to even consider this, and it tends to be so that even the half-assed half of
the conversion fails to materialize, let alone the other half that is
an absolute must
for such a conversion to be a feasible solution to migration over an API break.
Otherwise the maintenance cost of targeting two incompatible sides of the API
fence is still doubled.

More information about the Development mailing list