aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/test/gmock-more-actions_test.cc
Commit message (Collapse)AuthorAgeFilesLines
* Comments changes, no functionality changesGennadiy Civil2018-08-141-2/+1
|
* mergingGennadiy Civil2018-04-131-1/+2
|
* more fixing osx libstd++ bugsGennadiy Civil2018-04-121-1/+2
|
* merging, fix OSX issueGennadiy Civil2018-04-121-1/+2
|
* mergingGennadiy Civil2018-04-121-9/+5
|
* Use std::string and ::string explicitly in gtest and gmock code.Nico Weber2017-05-151-74/+77
| | | | | | | | | 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.
* Googlemock has some tuples containing lvalue refs in its unit tests.Billy Donahue2015-09-071-2/+5
| | | | | | | | | | | | | | | 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 .
* move googlemock files into googlemock/ subdirBilly Donahue2015-08-251-0/+705