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?

-- 
Giuseppe D'Angelo
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to