> BTW, shouldn't this one also have a "v" somewhere, like _qsv?
If there's a chance of adding an owning class for Latin-1 in future, it might make sense to reserve _L1 for it and add "v" for QLatin1StringView literal. On the other hand, we can call the literal operator for the owning class _L1s, and save some typing for the QLatin1StringView users (which, I guess, would be more common to use). Best regards, Sona > -----Original Message----- > From: Development <[email protected]> On Behalf Of > Thiago Macieira > Sent: Friday, March 11, 2022 4:39 PM > To: [email protected] > Subject: Re: [Development] Renaming QLatin1String to QLatin1StringView > > On Friday, 11 March 2022 00:46:16 PST Sona Kurazyan wrote: > > s. In Qt 7, QLatin1StringView will become "the real" class for Latin-1 > > string view, and QLatin1String will be kept as alias to it. > > I'd like to say I support this, at least as far as 7.0 with just the alias. > > When or if ever we drop the QLatin1String name and even if we ever add a > new class is a subject for much later and doesn't have to be taken now. But > unless we do the change Sona is proposing now, we that option wouldn't be > on the table. > > > Note that Qt 6.4 introduces a literal operator""_L1 for constructing > > Latin-1 string literals, to minimize the porting effort from > > QLatin1String to QLatin1StringView. > > BTW, shouldn't this one also have a "v" somewhere, like _qsv? > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel DPG Cloud Engineering > > > > _______________________________________________ > Development mailing list > [email protected] > https://lists.qt-project.org/listinfo/development _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
