[Development] QUIP 6: removing top-level const from return types

[Marc Mutz]

On Tuesday 23 May 2017 08:36:00 Lars Knoll wrote:
> But what I dislike is the fact that we get different signatures on
> different platforms (because we can't change this on MSVC without breaking
> BC).

So... if MSVC mangles the return type, does that mean that we can _overload_

   const QPixmap pixmap() const;
   QPixmap pixmap() const;

? The we can keep the old function in the DLL, but new code only sees the new 
signature.

BTW: https://codereview.qt-project.org/164690

BTW2: Please free this discussion from the fact that the change is on 
QSplashScreen. We're talking about removing TLC from return types, and that 
would also disallow the QStringBuilder change and https://codereview.qt-
project.org/93161, too, which clearly have had a higher (positive) impact than 
the QSplashScreen change. But allowing the change for QRegion and 
QStringBuilder, but not for QSplashScreen is the worst-possible outcome, as it 
would not help direct such decisions in the future.

Thanks,
Marc

-- 
Marc Mutz <marc.mutz at kdab.com> | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts