[Interest] QString , QStringLiteral, QLatin1String, char16_t and u" my char16 string literal"

[Thiago Macieira]

On segunda-feira, 2 de maio de 2016 16:58:26 PDT Gunnar Roth wrote:
> Hello,
> I have some questions about QString etc.
>  
> 1. What should I just, QStringLiteral or QLatin1String ? Old discussion
> (around 2011-2012) said QStringLiteral, but in gerrit a lot of changes from
> StrinLiteral to Latin1String orccured lately. 

All three. Use the one that makes most sense for the context at hand. I had an 
entire presentation at Qt Developer Days two years ago about this.

> 2. Will there be a char16_t constructor for QString and char16_t overloads
> for +, += etc? If not why not?  

There's QString::fromUtf16 overload for it. Adding a constructor overload is 
easy and that's probably an oversight.

Adding overloads to everything else that has QLatin1String would be really 
nice, but not an easy task.

> 3. Will the be support for fast concat with QStringBuilder and char16_t?

No one has studied the problem.

>  
> I made my own support for this:
>  
[cut]

Please submit it via the code review tool. I don't know if there will be side-
effects to this, but it looks interesting.

> Regards,
> Gunnar Roth


-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center