googletest/googlemock/src
Arthur O'Dwyer 766ac2e1a4 Remove all uses of GTEST_DISALLOW_{MOVE_,}ASSIGN_.
None of these are strictly needed for correctness.
A large number of them (maybe all of them?) trigger `-Wdeprecated`
warnings on Clang trunk as soon as you try to use the implicitly
defaulted (but deprecated) copy constructor of a class that has
deleted its copy assignment operator.

By declaring a deleted copy assignment operator, the old code
also caused the move constructor and move assignment operator
to be non-declared. This means that the old code never got move
semantics -- "move-construction" would simply call the defaulted
(but deprecated) copy constructor instead. With the new code,
"move-construction" calls the defaulted move constructor, which
I believe is what we want to happen. So this is a runtime
performance optimization.

Unfortunately we can't yet physically remove the definitions
of these macros from gtest-port.h, because they are being used
by other code internally at Google (according to zhangxy988).
But no new uses should be added going forward.
2020-04-23 22:22:07 -04:00
..
gmock_main.cc Revert "remove MSVC workaround: wmain link error in the static library" 2019-11-27 15:01:03 +01:00
gmock-all.cc Comments changes, no functionality changes 2018-08-14 14:04:07 -04:00
gmock-cardinalities.cc Googletest export 2018-12-03 12:54:11 -05:00
gmock-internal-utils.cc restore mistakenly removed iffs in their explicit form 2019-08-20 12:14:22 +02:00
gmock-matchers.cc Remove all uses of GTEST_DISALLOW_{MOVE_,}ASSIGN_. 2020-04-23 22:22:07 -04:00
gmock-spec-builders.cc Merge pull request #2497 from thejcannon:handle_null_filename 2019-10-10 09:21:47 -04:00
gmock.cc restore mistakenly removed iffs in their explicit form 2019-08-20 12:14:22 +02:00