Lines Matching refs:matchers

556 argument matchers:
862 You can use matchers to match arguments that have a certain property:
882 You can build complex matchers from existing ones using `AllOf()`,
901 Matchers are function objects, and parametrized matchers can be composed just
919 gMock matchers are statically typed, meaning that the compiler can catch your
1091 matchers.
1093 As a convenience and example, gMock provides some matchers for 2-tuples,
1095 [Multi-argument Matchers](reference/matchers.md#MultiArgMatchers) for the
1108 matchers were not allowed to participate.
1126 Since you can build complex matchers from simpler ones easily using gMock, this
1148 gMock provides a set of built-in matchers for matching arguments with expected
1149 values—see the [Matchers Reference](reference/matchers.md) for more information.
1174 when you use matchers like `Eq(bar)`, `Le(bar)`, and so on.
1249 can be useful when creating combined matchers.
1266 C++ functions often take pointers as arguments. You can use matchers like
1267 `IsNull()`, `NotNull()`, and other comparison matchers to match a pointer, but
1308 Most matchers can be simply defined using [the MATCHER* macros](#NewMatchers),
1311 suitable, especially for matchers that will be widely reused.
1409   // Or, an array of element matchers.
1459 implementation object. Copying matchers is allowed and very efficient, as only
1481 invoked. Therefore, all matchers must be *purely functional*: they cannot have
1486 it is one of the standard matchers, or a custom matcher). In particular, a
1688 the arguments match the matchers in the second `EXPECT_CALL()`, but not those in
2614 Just like matchers, a gMock action object consists of a pointer to a ref-counted
3190 matchers? Did you mess up the order of the `EXPECT_CALL`s? Or is the code under
3290 invoked. Therefore, all matchers must be functionally pure. See
3293 The `MATCHER*` family of macros can be used to define custom matchers easily.
3472 support multi-parameter matchers:
3542 matchers. Matchers that don't have a parameter or have only one parameter have
3552 You can overload matchers with different numbers of parameters:
3565 They also allow overloading matchers based on parameter types (as opposed to
3665 Expanding what we learned above to *polymorphic* matchers is now just as simple
3704 Defining matchers used to be somewhat more complicated, in which it required