1. 12 Feb, 2019 5 commits
    • Gennadiy Civil's avatar
      Merge pull request #2107 from ciband:feat/finish_platformio_support · b37574c1
      Gennadiy Civil authored
      PiperOrigin-RevId: 233108234
      b37574c1
    • Gennadiy Civil's avatar
      Merge pull request #2101 from MaEtUgR:fix-cmake-cygwin · b68ec344
      Gennadiy Civil authored
      PiperOrigin-RevId: 233096223
      b68ec344
    • Abseil Team's avatar
      Googletest export · 4f79e316
      Abseil Team authored
      Internal changes.
      
      PiperOrigin-RevId: 232953166
      4f79e316
    • Abseil Team's avatar
      Googletest export · 28a96d18
      Abseil Team authored
      Fix matcher comparisons for std::reference_wrapper.
      
      The googletest docs indicate that std::reference_wrapper should be used to for
      objects that should not be copied by the matcher (in fact, the ByRef() function
      is basically the same as a call to std::cref).
      
      However, for many types (such as std::string), the overloaded operator== will
      not resolve correctly. Specifically, this is problematic if operator== depends
      on template argument deduction, where the same type is named on LHS and RHS.
      
      Because template argument deduction happens before any implict conversions for
      purposes of overload resolution, attempting to compare T with
      std::reference_wrapper<T> simply looks like a comparison of unlike types.
      
      For exapmle, std::reference_wrapper<std::string> is implicitly convertible to
      'const std::string&', which would be able to choose an overload specialization
      of operator==. However, the implicit conversion can only happen after template
      argument deduction for operator==, so a specialization that would other be an
      applicable overload is never considered.
      
      Note also that this change only affects matchers. There are good reasons that
      matchers may need to transparently hold a std::reference_wrapper. Other
      comparisons (like EXPECT_EQ, et. al.) don't need to capture a reference: they
      don't need to defer evaluation (as in googlemock), and they don't need to avoid
      copies (as the call chain of matchers does).
      
      PiperOrigin-RevId: 232499175
      28a96d18
    • Abseil Team's avatar
      Googletest export · dda0df3b
      Abseil Team authored
      Internal change
      
      PiperOrigin-RevId: 232362580
      dda0df3b
  2. 05 Feb, 2019 4 commits
  3. 04 Feb, 2019 9 commits
  4. 01 Feb, 2019 4 commits
  5. 31 Jan, 2019 2 commits
  6. 30 Jan, 2019 5 commits
  7. 29 Jan, 2019 2 commits
  8. 28 Jan, 2019 2 commits
  9. 25 Jan, 2019 1 commit
  10. 24 Jan, 2019 1 commit
    • Adam Cozzette's avatar
      Fixed "make dist" · 46b81732
      Adam Cozzette authored
      I made a few updates to the Makefile.am files so that "make dist"
      succeeds and produces a usable tarball. We need this for protobuf
      because the protobuf tarballs include a bundled copy of googletest.
      46b81732
  11. 23 Jan, 2019 2 commits
    • Gennadiy Civil's avatar
      Merge pull request #2041 from ciband:chore/fix_library_json · bf07131c
      Gennadiy Civil authored
      PiperOrigin-RevId: 230554814
      bf07131c
    • Abseil Team's avatar
      Googletest export · fdc59ffd
      Abseil Team authored
      Add AllOfArray matcher that verifies a value matches all member of some array/container/list/set/..., e.g:
      EXPECT_THAT(1, AnyOfArray({1, 2, 3}))
      In the simplest form this is identical to AnyOf(1, 2, 3). But unlike that one it works on containers.
      
      Add AnyOfArray matcher that verifies a value matches any member of some
      array/container/list/set/...
      
      PiperOrigin-RevId: 230403653
      fdc59ffd
  12. 22 Jan, 2019 1 commit
    • Abseil Team's avatar
      Googletest export · 569fba4d
      Abseil Team authored
      Make internal FunctionMocker class final
      
      PiperOrigin-RevId: 230332778
      569fba4d
  13. 18 Jan, 2019 2 commits
    • Abseil Team's avatar
      Googletest export · 9518a574
      Abseil Team authored
      Fix mocking method arguments with templated copy constructors.
      
      A previous change removed workarounds for old compilers from googletest and googlemock. Unfortunately, a bit of code that started as a workaround for Symbian's C++ compiler is still needed to avoid copy/move constructor ambiguity when mocking functions with certain argument types.
      
      The test case added by this CL is extracted from Chrome's codebase, and was discovered while attempting to roll googletest.
      
      PiperOrigin-RevId: 229801765
      9518a574
    • Ayaz Salikhov's avatar
      7c4164bf