4 Commits

Author	SHA1	Message	Date
Derek Mauro	544c96ed5b	Remove FloatingPoint::Max() in favor of std::numeric_limits::max() ... 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	2023-01-24 08:41:35 -08:00
Abseil Team	238e4745c6	Generalize gmock-matchers_test to handle is_gtest_matcher-style matchers, too. ... PiperOrigin-RevId: 444586594 Change-Id: I0de9b40b3773e3047a492f050266967ea935ae3e	2022-04-26 09:49:03 -07:00
Derek Mauro	bf66935e07	Remove the legacy internal GTEST_DISALLOW_* macros ... PiperOrigin-RevId: 443715444 Change-Id: I3ffd54b63d2728ae4a668ee7875c8c3c8188087c	2022-04-22 11:26:03 -07:00
Mattias Ellert	073293463e	Split gmock-matchers_test into 4 smaller test #3653 ... The one large test does not link in limited memory environments Closes #3653 PiperOrigin-RevId: 436753193 Change-Id: Idd59b6509994fc642147b88279ee791cd1d7bdd0	2022-03-23 09:08:04 -07:00