| 09fd5b3ebfaac10b78bda664ec7f57fac74ef214 |
|
15-May-2017 |
Nico Weber <thakis@chromium.org> |
Use std::string and ::string explicitly in gtest and gmock code.
This merges a Google-internal change (117235625).
Original CL description:
This CL was created manually in about an hour with sed, a Python script
to find all the places unqualified 'string' was mentioned, and some help
from Emacs to add the "std::" qualifications, plus a few manual tweaks.
/external/googletest/googlemock/test/gmock-more-actions_test.cc
|
| f19b060075e89ac7ccd1744b30d41b755b92a10a |
|
08-Sep-2015 |
Billy Donahue <billydonahue@google.com> |
Googlemock has some tuples containing lvalue refs in its unit tests.
These tuples are created with make_tuple, which is given temporaries.
The make_tuple is in a function argument list.
A possibly overzealous static_assert in libc++'s std::tuple ctor
is firing in our 'Perform(make_tuple("hi"))' calls, so
we can't use its make_tuple here. Instead we will use
explicitly-constructed tuples constructed from non-temporary strings.
Workaround for llvm bug:
https://llvm.org/bugs/show_bug.cgi?id=20855
An alternative to https://github.com/google/googletest/pull/580 .
/external/googletest/googlemock/test/gmock-more-actions_test.cc
|
| affb09edf0dfac4e8570f99ed5af09543a7ffe4f |
|
25-Aug-2015 |
Billy Donahue <billydonahue@google.com> |
move googlemock files into googlemock/ subdir
/external/googletest/googlemock/test/gmock-more-actions_test.cc
|