[Development] How qAsConst and qExchange lead to qNN

[Thiago Macieira]

On Wednesday, 9 November 2022 02:52:15 PST Marc Mutz via Development wrote:
> This is the same effect we have with Q*StringView, incl. avoidance of
> caller-side construction and destruction of owning containers.

Indeed, which is WRONG.

Our API should default to passing QStrings for simplicity and not to confuse 
the user. The fact that I cannot wrote:

  foo(u"bar');

if foo takes a QString is MESSED UP.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering