aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/scripts/fuse_gmock_files.py
diff options
context:
space:
mode:
authorBilly Donahue <billydonahue@google.com>2015-09-07 22:32:56 -0400
committerBilly Donahue <billydonahue@google.com>2015-09-07 22:32:56 -0400
commitf19b060075e89ac7ccd1744b30d41b755b92a10a (patch)
treeae0c43fb177e949b18a042ea7102d05e688c164a /googlemock/scripts/fuse_gmock_files.py
parent99166db7545b56e0e34e1ce39932a1d411169b18 (diff)
downloadgoogletest-f19b060075e89ac7ccd1744b30d41b755b92a10a.tar.gz
googletest-f19b060075e89ac7ccd1744b30d41b755b92a10a.tar.bz2
googletest-f19b060075e89ac7ccd1744b30d41b755b92a10a.zip
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 .
Diffstat (limited to 'googlemock/scripts/fuse_gmock_files.py')
0 files changed, 0 insertions, 0 deletions