[Development] HEADS-UP: QStringLiteral
Tor Arne Vestbø
Tor.arne.Vestbo at qt.io
Wed Aug 21 18:17:24 CEST 2019
> On 21 Aug 2019, at 17:58, Thiago Macieira <thiago.macieira at intel.com> wrote:
> On Wednesday, 21 August 2019 08:16:42 PDT Tor Arne Vestbø wrote:
>> That’s what I was hoping. We have QFooLiteral today to let the compiler do
>> the work up front, isn’t it possible with newer c++ standards to have that
>> happen automatically without an explicit QFooLiteral?
> Yes, it's possible.
> But do we want to?
> Remember that QStringLiteral today has a drawback: if you
> unload the plugin it came from, any left-over uses of it may crash. That's one
> of the many reasons we don't unload plugins, but other people might.
Is that the only drawback? Is that the only reason we’re not doing it?
On macOS plugins are never unloaded. Could the behaviour be dependent on whether or not we’re building a plugin?
More information about the Development