- 29 Nov, 2022 1 commit
-
-
Abseil Team authored
Disables `-Wunused-member-function` and `-Wused-but-marked-unused` that trigger via `MOCK_METHOD()` and `EXPECT_THAT()` macros. Fixes: #4052, #4055 PiperOrigin-RevId: 491647393 Change-Id: I8e2ad838156fa8c7e9dccd1740af797e694992b6
-
- 22 Aug, 2022 1 commit
-
-
Hardik Vala authored
PiperOrigin-RevId: 469171380 Change-Id: Ic75fc0523924e40e620552d4c04b79dad22a68e0
-
- 29 Jul, 2022 1 commit
-
-
Abseil Team authored
PiperOrigin-RevId: 463961734 Change-Id: Ib62e320a745c190955f181c1f4f12e4cd407ef22
-
- 25 Jul, 2022 1 commit
-
-
Dino Radakovic authored
Fixes #3937 PiperOrigin-RevId: 463180144 Change-Id: I21b528acc4c3f3aba4234642be01fcead7fe7f00
-
- 01 Jul, 2022 2 commits
- 27 Jun, 2022 1 commit
-
-
assafpr authored
master branch changed to main in link
-
- 22 Jun, 2022 1 commit
-
-
assafpr authored
-
- 27 May, 2022 2 commits
-
-
Aaron Jacobs authored
Do this by ripping out the "untyped perform action" machinery, which isn't necessary: we can simply template the entry point on the result type, and use RAII to avoid the need to special case void. This makes it easier to understand the code and harder to introduce type-related undefined behavior, to boot. PiperOrigin-RevId: 451493451 Change-Id: I225305f83164752ca92f2916721972eafba33168
-
Aaron Jacobs authored
Previously this excluded callables that return non-moveable types. This is the same as the [libc++ std::is_invocable_r bug](https://github.com/llvm/llvm-project/issues/55346) fixed by [this commit](https://github.com/llvm/llvm-project/commit/c3a24882903d): it's wrong to use std::is_convertible for checking the return type, since (despite its name) that doesn't check the standard-defined notion of "implicitly convertible". Instead we must base the check on whether the source type can be used as an argument to a function that accepts the destination type. PiperOrigin-RevId: 451341205 Change-Id: I2530051312a0361ea7a2ce26993ae973c9242089
-
- 13 May, 2022 1 commit
-
-
Aaron Jacobs authored
`Return(x)` can now be used directly with `WillOnce` (the only place it makes sense in the type system), without using `ByMove`. PiperOrigin-RevId: 448380066 Change-Id: Ia71cc60ccbc3b99720662731a2d309735a5ce7c8
-
- 12 May, 2022 1 commit
-
-
Aaron Jacobs authored
It doesn't make semantic sense for the conversion to modify the input, and the fact that it's allowed to do so appears to have just been a historical accident. PiperOrigin-RevId: 448135555 Change-Id: Id10f17af38cf3947ee25fe10654d97527173ebfc
-
- 11 May, 2022 2 commits
-
-
Aaron Jacobs authored
Better document requirements, API decisions, and historical accidents. Make an implicit conversion easier and in a more appropriate place, and ease the burden of some assertions in the conversion operator. Stop using the legacy ActionInterface style for defining the action. PiperOrigin-RevId: 447894892 Change-Id: I179e23ec2abdd9bf05c204ab18dbb492f1372e8e
-
Aaron Jacobs authored
So that it can be referenced in conversion operators for actions that need to know the concrete return type. PiperOrigin-RevId: 447889344 Change-Id: I643d3298bc8effd08741282a956c221f9d67d378
-
- 27 Apr, 2022 1 commit
-
-
Aaron Jacobs authored
Commit a070cbd9 added an implicit cast to this path but didn't leave a very clear explanation for why it was desirable, a clear example, or even test coverage. Add a better comment and a test that fails when the implicit cast is removed. PiperOrigin-RevId: 444871311 Change-Id: I127982fa8d5bce9b6d1b68177c12dc0709449164
-
- 26 Apr, 2022 3 commits
-
-
Aaron Jacobs authored
PiperOrigin-RevId: 444671005 Change-Id: I7df5f038caf17afb60d4fb35434ff0b656d4c954
-
Abseil Team authored
PiperOrigin-RevId: 444586594 Change-Id: I0de9b40b3773e3047a492f050266967ea935ae3e
-
Aaron Jacobs authored
This is necessary for generic support of these actions, since `DoAll` is a frequently-used action wrapper. PiperOrigin-RevId: 444561964 Change-Id: I02edb55e35ab4207fbd71e371255a319c8253136
-
- 22 Apr, 2022 1 commit
-
-
Derek Mauro authored
PiperOrigin-RevId: 443715444 Change-Id: I3ffd54b63d2728ae4a668ee7875c8c3c8188087c
-
- 13 Apr, 2022 1 commit
-
-
Aaron Jacobs authored
PiperOrigin-RevId: 441589196 Change-Id: Ic3e483ca70d72261046bad464d817f9dfd4bec65
-
- 09 Apr, 2022 1 commit
-
-
Abseil Team authored
This provides a type-safe way for an action to express that it wants to be called only once, or to capture move-only objects. It is a generalization of the type system-evading hack in ByMove, with the improvement that it works for _any_ action (including user-defined ones), and correctly expresses that the action can only be used with WillOnce. I'll make existing actions benefit in a future commit. PiperOrigin-RevId: 440496139 Change-Id: I4145d191cca5655995ef41360bb126c123cb41d3
-
- 04 Apr, 2022 1 commit
-
-
Abseil Team authored
PiperOrigin-RevId: 439389646 Change-Id: Ie34adcdd2b24378e85962efac53b7bb89ed93803
-
- 23 Mar, 2022 2 commits
-
-
Abseil Team authored
PiperOrigin-RevId: 436839469 Change-Id: I2bb90dce524c16bcc31569bb98772dcc62d08fbf
-
Mattias Ellert authored
The one large test does not link in limited memory environments Closes #3653 PiperOrigin-RevId: 436753193 Change-Id: Idd59b6509994fc642147b88279ee791cd1d7bdd0
-
- 18 Mar, 2022 1 commit
-
-
Brad Messer authored
-
- 15 Mar, 2022 1 commit
-
-
Abseil Team authored
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
-
- 10 Feb, 2022 1 commit
-
-
Abseil Team authored
Add a 3-arg overload for ResultOf() matcher that takes a description string for better error messages. PiperOrigin-RevId: 427598749 Change-Id: I8c7a5d7b2dde017641534f1c7eed8dd56c33e845
-
- 26 Jan, 2022 1 commit
-
-
Dino Radakovic authored
PiperOrigin-RevId: 424355706 Change-Id: I618e5574b4b2c56a343905c20d8cc6d2a70cbcd1
-
- 27 Dec, 2021 1 commit
-
-
Abseil Team authored
PiperOrigin-RevId: 418497526 Change-Id: Ie53c3c0810c10a32cbcb941e3ca1ee8fb1ddd9f9
-
- 22 Dec, 2021 1 commit
-
-
Derek Mauro authored
unifying the behavior between Bazel and CMake This fixes one of the CI failures on Windows PiperOrigin-RevId: 417872531 Change-Id: I156989323b7e6d4a4420f4f9691b078829db933d
-
- 03 Dec, 2021 1 commit
-
-
Abseil Team authored
PiperOrigin-RevId: 413963503 Change-Id: I33440780bf087698f4e4325399227405885430b3
-
- 15 Nov, 2021 1 commit
-
-
Taylor Cramer authored
The previous error message could be misinterpreted to mean that `Times` could not be used in combination with `WillRepeatedly`, when in fact the call to `Times` just needs to happen *first*. PiperOrigin-RevId: 410070405 Change-Id: I747d34a4334cf2e56d589dcad3a08a8f322d77c8
-
- 12 Nov, 2021 1 commit
-
-
Abseil Team authored
Fix typo in gmock-matchers_test.cc: CanDescribeNegationOfExpectingOneElment => CanDescribeNegationOfExpectingOneElement PiperOrigin-RevId: 409484263 Change-Id: I7448d6f04a9868602e0bc8dec40ea3eb63d3e387
-
- 05 Nov, 2021 1 commit
-
-
Raul Tambre authored
This was deprecated by P0174 in C++17.
-
- 03 Nov, 2021 1 commit
-
-
Abseil Team authored
Internal change PiperOrigin-RevId: 405710296
-
- 28 Sep, 2021 1 commit
-
-
Abseil Team authored
Ensure `.what()` is printed in `ThrowsMessage(...)` to address https://github.com/google/googletest/issues/3582 Closes #3582 PiperOrigin-RevId: 399462851
-
- 24 Sep, 2021 1 commit
-
-
Christian Clauss authored
-
- 17 Sep, 2021 1 commit
-
-
Vertexwahn authored
-
- 15 Sep, 2021 1 commit
-
-
Abseil Team authored
Introduce GMOCK_FLAG_GET and GMOCK_FLAG_SET macros. PiperOrigin-RevId: 396649214
-
- 04 Aug, 2021 1 commit
-
-
Abseil Team authored
Introduce a new matcher for unescaping Base-64 strings to gmock. PiperOrigin-RevId: 388471904
-