Skip to content

GitLab

Switch branch/tag
  1. 28 Apr, 2023 2 commits
  3. 24 Apr, 2023 1 commit
    • Patryk Gawroński's avatar
      gmock: fix issue #4222 · 51eeae5a
      Patryk Gawroński authored 
      Rename 'Result' struct to 'NonMoveableStruct' in
gmock-spec-builders_test.cc in ExpectCallTest.NonMoveableType test
      51eeae5a
  5. 21 Apr, 2023 2 commits
  7. 20 Apr, 2023 1 commit
  9. 14 Apr, 2023 1 commit
  11. 11 Apr, 2023 1 commit
    • Abseil Team's avatar
      Fix FunctionMocker compilation slowdown in 9d21db9e · 8fa9461c
      Abseil Team authored 
      The slowdown appears to be due to an implicit conversion of distinct (yet semantically identical) lambdas to `std::function`. Lifting out the lambdas into functors that don't get re-instantiated reduces compilation times by nearly half.

Fixes #4156

PiperOrigin-RevId: 523447948
Change-Id: Ib0ae0761a54d7b1f2b706b14b2858eedf47e2297
      8fa9461c
  13. 28 Mar, 2023 1 commit
  15. 23 Mar, 2023 1 commit
  17. 21 Mar, 2023 1 commit
    • Abseil Team's avatar
      Internal Code Change · e9faae17
      Abseil Team authored 
      PiperOrigin-RevId: 518213370
Change-Id: I88d0acc195dadf8d03cd15c8534c721141db14ea
      e9faae17
  19. 20 Mar, 2023 1 commit
  21. 11 Mar, 2023 1 commit
    • Abseil Team's avatar
      Internal Code Change · 391ce627
      Abseil Team authored 
      PiperOrigin-RevId: 515855852
Change-Id: I8016eefd45c36089e189bbd1ebbe9fdabe68255b
      391ce627
  23. 10 Mar, 2023 1 commit
  25. 07 Mar, 2023 1 commit
    • Abseil Team's avatar
      Internal Code Change · 1a727c27
      Abseil Team authored 
      PiperOrigin-RevId: 514678702
Change-Id: I5b0089d905152ccb85022be395ed340e42586234
      1a727c27
  27. 06 Mar, 2023 2 commits
  29. 03 Mar, 2023 1 commit
    • Abseil Team's avatar
      Internal Code Change · cead3d57
      Abseil Team authored 
      PiperOrigin-RevId: 513770561
Change-Id: I82fbed177c6ba4e2e5b776ae3e0255c868e32e25
      cead3d57
  31. 28 Feb, 2023 1 commit
    • Yonggang Luo's avatar
      Fixes the test gmock_output_test.py with MSVC · 6f1c4b3d
      Yonggang Luo authored 
      

For MSVC, gmock_output_test.py output struct std::pair<int,bool>, for GCC, it's output
std::pair<int, bool>, it's not the same, my intention is getting these to be same by removing
struct  for MSVC's outptu, and strip redundant space for GCC.

As a by-product,
```
#ifdef _MSC_VER
#define ERROR_DESC "class std::runtime_error"
#else
#define ERROR_DESC "std::runtime_error"
#endif
```
can be simplified to

```
#define ERROR_DESC "std::runtime_error"
```
Signed-off-by: default avatarYonggang Luo <luoyonggang@gmail.com>
      6f1c4b3d
  33. 16 Feb, 2023 1 commit
  35. 09 Feb, 2023 1 commit
  37. 07 Feb, 2023 2 commits
  39. 06 Feb, 2023 1 commit
  41. 01 Feb, 2023 3 commits
  43. 30 Jan, 2023 2 commits
  45. 25 Jan, 2023 2 commits
  47. 24 Jan, 2023 2 commits
    • Tom Hughes's avatar
      Fix formatting of C++ files · 24917105
      Tom Hughes authored 
      PiperOrigin-RevId: 504325204
Change-Id: Iaa1d6d0ab1dccaaeef26f9cb109d530835499240
      24917105
    • Derek Mauro's avatar
      Remove FloatingPoint::Max() in favor of std::numeric_limits::max() · 544c96ed
      Derek Mauro authored 
      In #4113 a user says Max clashes with a macro. Since it is only used in
a test, use std::numeric_limits::max() instead.

Note that in headers, the macro issue can be mitigated with
parenthesis like this: `(std::numeric_limits<T>::max)()`

PiperOrigin-RevId: 504284906
Change-Id: Ibf430caec1a6afdf6b303534fec6a4fd00a6373f
      544c96ed
  49. 17 Jan, 2023 2 commits
  51. 12 Jan, 2023 1 commit
    • Tom Hughes's avatar
      Fix -Wshadow warnings · 356fc301
      Tom Hughes authored 
      ../googlemock/test/gmock-actions_test.cc:687:36: warning: declaration of ‘v’ shadows a member of ‘testing::{anonymous}::ReturnTest_SupportsReferenceLikeReturnType_Test::TestBody()::Result’ [-Wshadow]
  687 |     Result(const std::vector<int>& v) : v(&v) {}  // NOLINT
      |            ~~~~~~~~~~~~~~~~~~~~~~~~^
../googlemock/test/gmock-actions_test.cc:686:29: note: shadowed declaration is here
  686 |     const std::vector<int>* v;
      |                             ^

../googlemock/test/gmock-actions_test.cc: In constructor ‘testing::{anonymous}::ReturnTest_PrefersConversionOperator_Test::TestBody()::Out::Out(int)’:
../googlemock/test/gmock-actions_test.cc:720:28: warning: declaration of ‘x’ shadows a member of ‘testing::{anonymous}::ReturnTest_PrefersConversionOperator_Test::TestBody()::Out’ [-Wshadow]
  720 |     explicit Out(const int x) : x(x) {}
      |                  ~~~~~~~~~~^
../googlemock/test/gmock-actions_test.cc:718:9: note: shadowed declaration is here
  718 |     int x;
      |         ^

PiperOrigin-RevId: 501580618
Change-Id: I584710fbbe440ec724f88746e51f3be5653c32d5
      356fc301
  53. 05 Jan, 2023 1 commit
  55. 04 Jan, 2023 1 commit
  57. 15 Dec, 2022 1 commit
    • Abseil Team's avatar
      Shut up a Clang warning. · 3fa7f983
      Abseil Team authored 
      Clang warns on this pattern because it looks like the author might
have meant to use the value of the first part of the comma operator,
so it warns that it isn't being used. The cast here signals to Clang
that this behavior is intentional.

This was discovered while updating gmock in Android. Clang's -Wcomma
warning is on by default with either -Wall or -Werror, so users of
gmock with those on in combination with -Werror are unable to build
without this fix.

PiperOrigin-RevId: 495655990
Change-Id: Iaf27e2199669f5b6185a877738234e551b6b6556
      3fa7f983
  59. 12 Dec, 2022 1 commit