summaryrefslogtreecommitdiffstats
path: root/googlemock/include/gmock/internal
Commit message (Collapse)AuthorAgeFilesLines
* Replace infinite recursion call (intentionally invoking undefined behavior ↵Abseil Team2022-04-131-3/+6
| | | | | | | to indicate unreachability) with explicit unreachability marker. PiperOrigin-RevId: 441474979 Change-Id: I1fcbb437026631212fec954c663482bb7e1cf819
* Use the Abseil flags library when Abseil is presentDerek Mauro2022-04-041-20/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | When built with `--define=absl=1` under Bazel, GoogleTest flags use ABSL_FLAG instead of GoogleTest's own implementation. There are some minor behavior differences in this mode. The most notable difference is that unrecognized flags result in a flag parsing error, and are not returned to the user though a modified argc/argv, unless they appear after the positional argument delimiter ("--"). For example, to pass a non-Abseil flag, you would have to do ./mytest --gtest_color=false -- --myflag=myvalue The documentation at https://abseil.io/docs/cpp/guides/flags may be helpful in understanding the behavior. There are some other minor differences. For example, passing --help results in the program returning 1 instead of 0. https://github.com/google/googletest/issues/3646 PiperOrigin-RevId: 439312700 Change-Id: Id696a25f50f24a5b1785c45ca8fa59794f86fd5c
* Running clang-format over all of GoogleTestAbseil Team2022-03-152-43/+51
| | | | | | | | | | | | | | | | A few tests are examining code locations and looking af the resulting line numbers to verify that GoogleTest shows those to users correctly. Some of those locations change when clang-format is run. For those locations, I've wrapped portions in: // clang-format off ... // clang-format on There may be other locations that are currently not tickled by running clang-format. PiperOrigin-RevId: 434844712 Change-Id: I3a9f0a6f39eff741c576b6de389bef9b1d11139d
* Consistently apply IWYU pragmas across googletest and googlemock headersAbseil Team2022-01-185-4/+17
| | | | | PiperOrigin-RevId: 422559250 Change-Id: I9f630f2186724950e5e9fbd7093d5264e8bf0a71
* Include the param names in the generated description of the MATCHER_P matchers.Abseil Team2021-12-271-1/+5
| | | | | PiperOrigin-RevId: 418497526 Change-Id: Ie53c3c0810c10a32cbcb941e3ca1ee8fb1ddd9f9
* Support std::reference_wapper as a smart pointer type in gmockAbseil Team2021-12-031-0/+7
| | | | | PiperOrigin-RevId: 413963503 Change-Id: I33440780bf087698f4e4325399227405885430b3
* Internal changeAbseil Team2021-09-231-6/+6
| | | | PiperOrigin-RevId: 397651677
* Googletest exportAbseil Team2021-09-152-11/+31
| | | | | | Introduce GMOCK_FLAG_GET and GMOCK_FLAG_SET macros. PiperOrigin-RevId: 396649214
* Merge pull request #3504 from duianto:patch-1Derek Mauro2021-08-131-1/+1
|\ | | | | | | PiperOrigin-RevId: 390486428
| * Typo, double "the"refs/pull/3504/headduianto2021-07-291-1/+1
| |
* | Googletest exportAbseil Team2021-08-041-0/+2
|/ | | | | | Introduce a new matcher for unescaping Base-64 strings to gmock. PiperOrigin-RevId: 388471904
* Googletest exportAbseil Team2021-07-225-10/+0
| | | | | | Delete GOOGLETEST_CM.* tags from C++ code. PiperOrigin-RevId: 386268534
* Googletest exportAbseil Team2021-03-166-18/+18
| | | | | | Internal change PiperOrigin-RevId: 362040448
* Googletest exportAbseil Team2021-02-186-17/+17
| | | | | | Make include guards conform with https://google.github.io/styleguide/cppguide.html#The__define_Guard, attempt #2 PiperOrigin-RevId: 357056902
* Googletest exportAbseil Team2021-02-116-17/+17
| | | | | | Revert include guard fix PiperOrigin-RevId: 356588893
* Googletest exportAbseil Team2021-02-116-17/+17
| | | | | | Make include guards conform with https://google.github.io/styleguide/cppguide.html#The__define_Guard PiperOrigin-RevId: 355882793
* Googletest exportAbseil Team2021-02-051-3/+3
| | | | | | Remove uses of GTEST_HAS_TYPED_TEST_P and GTEST_HAS_TYPED_TEST. PiperOrigin-RevId: 353935996
* Googletest exportAbseil Team2021-01-264-216/+1
| | | | | | Stop using pump for generating internal/custom/gmock-generated-actions.h PiperOrigin-RevId: 352660735
* Googletest exportAbseil Team2021-01-261-0/+12
| | | | | | Internal change PiperOrigin-RevId: 352607401
* Googletest exportAbseil Team2021-01-264-17/+204
| | | | | | Merge CONTRIBUTORS, delete LICENSEs in googletest/ and googlemock/ PiperOrigin-RevId: 352558822
* Googletest exportAbseil Team2020-12-071-15/+2
| | | | | | | | | Add a `Pointer` matcher as an analog to `Pointee`. Similar to `Pointee`, `Pointer` works with either raw or smart pointers and allows creating a matcher like Pointer(Eq(foo)) for smart pointers. PiperOrigin-RevId: 346164768
* Googletest exportAbseil Team2020-05-071-3/+3
| | | | | | | | | | | | | | | | Fix `-Wgnu-zero-variadic-macro-arguments` in GMock Passing zero arguments to the variadic part of a macro is a GNU extension and triggers warnings when build projects using GMock with `-pedantic`. - Fix uses of `GMOCK_PP_INTERNAL_16TH` to always receive at least 17 arguments. (this was triggered when `GMOCK_PP_NARG` or `GMOCK_PP_HAS_COMMA` were used with an argument containing no commas). - Fix `GMOCK_PP_HEAD` to append a dummy unused argument so that `GMOCK_PP_INTERNAL_HEAD` always has two arguments. PiperOrigin-RevId: 310414611
* Googletest exportAbseil Team2020-05-011-4/+6
| | | | | | Rewrite ReturnNew action without using pump. PiperOrigin-RevId: 308219616
* Googletest exportAbseil Team2020-02-071-0/+8
| | | | | | | | Get rid of gmock-generated-matchers.h and gmock-generated-matchers.h.pump. Stop using pump for MATCHER* macroses generation. PiperOrigin-RevId: 293878808
* Googletest exportAbseil Team2019-11-222-7/+5
| | | | | | | | | | | | | Use standard C++11 integer types in gtest-port.h. Remove testing::internal::{Int,Uint}{32,64} in favor of types guaranteed to be in <cstdint> since C++11. Tests for built-in integer type coverage are switched from {Int,Uint}64 to [unsigned] long long, which is guaranteed by C++11 to exist and be at least 64-bit wide. PiperOrigin-RevId: 281565263
* Merge pull request #2514 from thejcannon:msvc_macro_issuevslashg2019-10-231-77/+31
|\ | | | | | | PiperOrigin-RevId: 276134684
| * Avoid recursive macrosrefs/pull/2514/headJoshua Cannon2019-10-111-22/+28
| |
| * Removing extraneous parenthesisJoshua Cannon2019-10-111-1/+1
| |
| * Evaluate and cat NARG in different macrosJoshua Cannon2019-10-111-8/+8
| |
| * Fix preprocessor testsJoshua Cannon2019-10-111-3/+1
| |
| * Workaround MSVC VA_ARGS weirdnessJoshua Cannon2019-10-111-66/+19
| |
* | Googletest exportAbseil Team2019-10-221-65/+27
| | | | | | | | | | | | | | | | Remove bool_constant in favor of std::integral_constant<bool, ...>; The one non-trivial use of bool_constant has been changed to have significantly fewer template specializations. PiperOrigin-RevId: 275842490
* | Googletest exportAbseil Team2019-10-111-2/+1
| | | | | | | | | | | | | | Fix the O(n^2) number of instantiations in ElemFromList. It is now O(n). It still has O(1) instantiation depth. PiperOrigin-RevId: 273980821
* | square away the stuff that hasn't been merged in a manual reviewKrystian Kuzniarek2019-09-161-2/+0
|/ | | | | This fixes up ab8f346b (a manual merge) that has abandoned some things from PR #2395.
* Googletest exportkuzkry2019-09-161-5/+4
| | | | | | | | | Merge 3bdefdb473d304803d2a38e2a2cd5cdc1827c3bd into fb49e6c164490a227bbb7cf5223b846c836a0305 Closes #2407 COPYBARA_INTEGRATE_REVIEW=https://github.com/google/googletest/pull/2407 from kuzkry:StaticAssertTypeEq 3bdefdb473d304803d2a38e2a2cd5cdc1827c3bd PiperOrigin-RevId: 269255328
* Merge pull request #2387 from kuzkry:iffShaindel Schwartz2019-09-121-10/+10
|\ | | | | | | PiperOrigin-RevId: 268693457
| * restore mistakenly removed iffs in their explicit formrefs/pull/2387/headKrystian Kuzniarek2019-08-201-10/+10
| | | | | | | | | | Due to confusion arisen from "iff" standing for "if and only if", this commit uses the latter.
* | Googletest exportkuzkry2019-09-061-4/+0
| | | | | | | | | | | | | | | | | | Merge 7f4f58da20e1066a888d3e4bcbef541db798a605 into 90a443f9c2437ca8a682a1ac625eba64e1d74a8a Closes #2395 COPYBARA_INTEGRATE_REVIEW=https://github.com/google/googletest/pull/2395 from kuzkry:custom-type-traits-remove_reference 7f4f58da20e1066a888d3e4bcbef541db798a605 PiperOrigin-RevId: 266189044
* | Merge pull request #2382 from kuzkry:dead-metafunctionGennadiy Civil2019-08-271-13/+0
|\ \ | | | | | | | | | PiperOrigin-RevId: 265730482
| * | remove a dead metafunctionrefs/pull/2382/headKrystian Kuzniarek2019-08-161-13/+0
| | |
* | | Googletest exportkuzkry2019-08-231-13/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | Merge b8ca465e73ac0954a0c9eec2a84bdd8913d5763b into 90a443f9c2437ca8a682a1ac625eba64e1d74a8a Closes #2396 COPYBARA_INTEGRATE_REVIEW=https://github.com/google/googletest/pull/2396 from kuzkry:custom-type-traits-true/false_type-and-bool_constant b8ca465e73ac0954a0c9eec2a84bdd8913d5763b PiperOrigin-RevId: 265064856
* | | Merge pull request #2394 from ↵Xiaoyi Zhang2019-08-231-14/+3
|\ \ \ | | | | | | | | | | | | | | | | | | | | kuzkry:custom-type-traits-duplication-of-custom-index_sequence PiperOrigin-RevId: 264863984
| * | | reuse IndexSequence from googletestrefs/pull/2394/headKrystian Kuzniarek2019-08-141-14/+3
| |/ /
* | | Merge pull request #2393 from kuzkry:custom-type-traits-remove_constXiaoyi Zhang2019-08-211-5/+5
|\ \ \ | |_|/ |/| | | | | PiperOrigin-RevId: 264652890
| * | remove a custom implementation of std::remove_constrefs/pull/2393/headKrystian Kuzniarek2019-08-131-5/+5
| |/
* | Merge pull request #2397 from kuzkry:custom-type-traits-is_referenceGennadiy Civil2019-08-191-4/+0
|\ \ | | | | | | | | | PiperOrigin-RevId: 264193098
| * | remove a custom implementation of std::is_referenceKrystian Kuzniarek2019-08-141-4/+0
| |/
* | Googletest exportAbseil Team2019-08-151-19/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | Remove legacy support for signed wchar_t and unsigned wchar_t. Clang now errors out on these types as well by default. Rather than making the condition for these types even more complicated, just remove the tests covering these types since they don't seem to justify the maintenance burden. We can reasonably expect these types to work in compilers that support them without needing specific tests for them since they are treated as standard integral types. PiperOrigin-RevId: 263577673
* | remove custom implementations of std::is_samerefs/pull/2399/headKrystian Kuzniarek2019-08-141-4/+0
|/
* fix typosrefs/pull/2356/headKrystian Kuzniarek2019-07-301-9/+9
|
generated by cgit v0.12 at 2024-09-01 06:19:40 (GMT)