tree 0152b79e116e3b510df1d817c64766e5737f9bf2
parent 5636d52baad683fbb51447a716d66cb06959e52f
author Ed Tanous <edtanous@google.com> 1620774772 -0700
committer Ed Tanous <edtanous@google.com> 1620774772 -0700

Make a string copy explicit

The newest version of gcc seems to flag on patterns like what was
included there, where we implicitly construct a string, then take a
reference to it.  So far as I'm aware, this has never caused an issue in
practice, but seems to be undefined behavior.

In a perfect world, I would change the left side of this to match the
input type of const char*, but that would require some interface changes
that I'd like to avoid to keep this change small and self contained
while we try to fix the build.

Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: Ic1ff16c02f6461894834432ccad285526ae41b3f