[llvm-dev] Passing Twine by value
David Blaikie via llvm-dev
llvm-dev at lists.llvm.org
Thu May 30 11:25:24 PDT 2019
I don't believe there's any correctness issue with passing Twine by value.
Not sure it'd even be a performance problem - the sizeof(Twine) looks like
it'd be small enough (like StringRef - though a bit bigger, StringRef
should be two words, Twine would be three) not to worry too much either way.
On Thu, May 30, 2019 at 12:14 AM Shoaib Meenai via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Twine.h says twines should only be accepted as const references in
> arguments, but there are a bunch of functions that take Twine by value
> (e.g. you'll find lots of them in CGObjCMac.cpp in clang). Is this just a
> potential performance issue, or are there potential correctness issues from
> passing a twine by value as well?
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev