[Development] QStringLiteral vs QLatin1String , foreach vs for range
Smith Martin
Martin.Smith at theqtcompany.com
Wed Jan 20 11:16:57 CET 2016
Here is a JIRA task for it:
https://bugreports.qt.io/browse/QTBUG-50548
________________________________________
From: Development <development-bounces at qt-project.org> on behalf of Marc Mutz <marc.mutz at kdab.com>
Sent: Wednesday, January 20, 2016 11:58 AM
To: development at qt-project.org
Subject: Re: [Development] QStringLiteral vs QLatin1String , foreach vs for range
On Wednesday 20 January 2016 08:19:04 Thiago Macieira wrote:
> On Wednesday 20 January 2016 08:12:58 André Somers wrote:
> > Where is this qAsConst coming from? When was it introduced? Where is it
> > documented?
>
> Commit 264c72837d6ff717a248dd180c2dfb45391c6aab, in dev. No api docs.
It was intended as private API for use within Qt. If the sentiment is that it
should be public, I'll add proper docs.
If the sentiment is also that we should start to discourage the use of
Q_FOREACH, then I'll add a \note to its docs pointing at qAsConst + range-for.
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 Experts
_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
More information about the Development
mailing list