mirror of
https://github.com/google/googletest.git
synced 2025-12-10 10:46:52 +08:00
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. |
||
|---|---|---|
| .. | ||
| BUILD.bazel | ||
| gmock_all_test.cc | ||
| gmock_ex_test.cc | ||
| gmock_leak_test_.cc | ||
| gmock_leak_test.py | ||
| gmock_link2_test.cc | ||
| gmock_link_test.cc | ||
| gmock_link_test.h | ||
| gmock_output_test_.cc | ||
| gmock_output_test_golden.txt | ||
| gmock_output_test.py | ||
| gmock_stress_test.cc | ||
| gmock_test_utils.py | ||
| gmock_test.cc | ||
| gmock-actions_test.cc | ||
| gmock-cardinalities_test.cc | ||
| gmock-function-mocker_nc_test.py | ||
| gmock-function-mocker_nc.cc | ||
| gmock-function-mocker_test.cc | ||
| gmock-generated-actions_test.cc | ||
| gmock-generated-matchers_test.cc | ||
| gmock-internal-utils_test.cc | ||
| gmock-matchers_test.cc | ||
| gmock-more-actions_test.cc | ||
| gmock-nice-strict_test.cc | ||
| gmock-port_test.cc | ||
| gmock-pp_test.cc | ||
| gmock-pp-string_test.cc | ||
| gmock-spec-builders_test.cc | ||
| pump_test.py | ||