Re: [Development] HEADS-UP: QStringLiteral

Hi, Isn't silly to have so many wrappers around a such a simple thing as strings? All the major frameworks out there (i.e. Java, C#) they have a single String which does all the magic. In Qt we have: QString, lost of QString::fromXXX, QLatin1String, QStringLiteral, QStringView, QByteArray

Re: [Development] HEADS-UP: QStringLiteral

another Drawback : it causes a global mutex to be executed on first use inside a block scope (c++11 static variable thread safety). Philippe On Tue, 20 Aug 2019 12:04:12 +0200 "Mutz, Marc via Development" wrote: > Hi, > > In light of a recent attempt to re-introduce QStringLiteral, relacing

[Development] HEADS-UP: QStringLiteral

Hi, In light of a recent attempt to re-introduce QStringLiteral, relacing QLatin1String, I'd like to remind everyone that QStringLiteral has a lot of drawbacks and should not be used unless it saves a memory allocation. Drawbacks include: - doubled storage requirements (2 bytes/char) over a

<    1   2