[Development] Question about QCoreApplicationData::*_libpaths
marc.mutz at kdab.com
Tue Jan 19 16:11:40 CET 2016
On Tuesday 19 January 2016 15:00:33 Marc Mutz wrote:
> 1. Tell people to use auto when receiving Qt containers returned from a
> 2. Tell people to stick to the std-compatible API subset.
> 3. Deprecate Q_FOREACH and recommend range-for (+ qAsConst(), where
4. Port as many internal containers (those that are not exposed in API) to std
> In Qt 6:
> 1. Implement the containers on top of std ones, dropping CoW, providing
> simple, fast (when moving), conversion between std and Qt containers.
> 2. Deprecate the std-incompatible API subset
> 3. Remove Q_FOREACH
> 4. Deprecate qAsConst()
5. Use Qt containers only in the interface, not the implementation.
> In Qt 7:
> 1. Drop all Qt container API use from the library, use only std ones.
> 2. Keep the Qt ones around as deprecated, in a separate compat library.
> 3. Drop qAsConst()
> In Qt 8:
> Remove the Qt ones.
> That easily spans 10-15 years, but at least we'd have an exit strategy.
> If, otoh, by Qt 6, we'd still continue doing nothing, as before, we'll
> lose another four years.
Marc Mutz <marc.mutz at kdab.com> | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
KDAB - The Qt Experts
More information about the Development