On Thursday, 23 April 2020 07:56:57 PDT Vitaly Fanaskov wrote:
> 1) Clang cannot compile all Qt-using codebases. Therefore, its tooling
> cannot work in all cases either.
> That's true, but on the other hand, covering at least a half of code bases
> would be a huge progress. I don't have
On 23/04/2020 15.22, Sérgio Martins via Development wrote:
Specially when talking about QList -> QVector, as QVector doesn't
guarantee the stability of references due to reallocation.
Nor with Qt6 QHash... still waiting to see how much code *that* silently
breaks.
--
Matthew
On 2020-04-23 14:55, Thiago Macieira wrote:
On Thursday, 23 April 2020 05:25:33 PDT Vitaly Fanaskov wrote:
Provide clang-based tools to (semi-)automatically port users' code
bases to
a new version of Qt. These tools might either fix a code or at least
add a
comment in potentially problematic
.
Vitaly
From: Development on behalf of Thiago
Macieira
Sent: Thursday, April 23, 2020 15:55
To: development@qt-project.org
Subject: [Development] Clang-based refactoring to Qt 6 (Proposal: Deprecate
QVector in Qt 6)
On Thursday, 23 April 2020 05:25:33 PDT
On Thursday, 23 April 2020 05:25:33 PDT Vitaly Fanaskov wrote:
> Provide clang-based tools to (semi-)automatically port users' code bases to
> a new version of Qt. These tools might either fix a code or at least add a
> comment in potentially problematic places where a user should correct the
>
