[Development] How qAsConst and qExchange lead to qNN
thiago.macieira at intel.com
Wed Nov 9 20:25:19 CET 2022
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:
if foo takes a QString is MESSED UP.
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
More information about the Development