On 06/02/2016 09:21 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> Several spots in the code malloc a string, then wrap it in a
>> QString, which has to duplicate the input. Adding a new
>> constructor with transfer semantics makes this pattern more
>> efficient, comparable to the just-a
Eric Blake writes:
> Several spots in the code malloc a string, then wrap it in a
> QString, which has to duplicate the input. Adding a new
> constructor with transfer semantics makes this pattern more
> efficient, comparable to the just-added transfer semantics to
> go from QString back to raw
Several spots in the code malloc a string, then wrap it in a
QString, which has to duplicate the input. Adding a new
constructor with transfer semantics makes this pattern more
efficient, comparable to the just-added transfer semantics to
go from QString back to raw string. Use the new
qstring_wr