> On 24 May 2017, at 00:35, Giuseppe D'Angelo <[email protected]> wrote: > > On Tue, May 23, 2017 at 11:56 PM, Thiago Macieira > <[email protected]> wrote: >> >> We are arguing whether the change makes the code uglier and is worth that >> ugliness. I'm not sold on that. Leave those const behind until Qt 6, unless >> you can show that engaging the move constructor is important. > > What about defining a (private) macro centrally and using it in those > places, as it has been proposed?
+1 on that. It avoids the uglyness of having a complicated #ifdef that we'd probably have in multiple places. It'll also ensure we can do the changes now and the we won't forget to fix it when we move over to Qt 6. Cheers, Lars _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
