Lines Matching refs:matcher

207 // Implements the Args() matcher.
481 Args(const InnerMatcher& matcher) {
482 return internal::ArgsMatcher<InnerMatcher>(matcher);
487 Args(const InnerMatcher& matcher) {
488 return internal::ArgsMatcher<InnerMatcher, k1>(matcher);
493 Args(const InnerMatcher& matcher) {
494 return internal::ArgsMatcher<InnerMatcher, k1, k2>(matcher);
499 Args(const InnerMatcher& matcher) {
500 return internal::ArgsMatcher<InnerMatcher, k1, k2, k3>(matcher);
505 Args(const InnerMatcher& matcher) {
506 return internal::ArgsMatcher<InnerMatcher, k1, k2, k3, k4>(matcher);
511 Args(const InnerMatcher& matcher) {
512 return internal::ArgsMatcher<InnerMatcher, k1, k2, k3, k4, k5>(matcher);
517 Args(const InnerMatcher& matcher) {
518 return internal::ArgsMatcher<InnerMatcher, k1, k2, k3, k4, k5, k6>(matcher);
524 Args(const InnerMatcher& matcher) {
526 k7>(matcher);
532 Args(const InnerMatcher& matcher) {
534 k8>(matcher);
540 Args(const InnerMatcher& matcher) {
542 k9>(matcher);
549 Args(const InnerMatcher& matcher) {
551 k9, k10>(matcher);
557 // ElementsAre() can be either a value or a matcher. We support up to
1176 // defines a matcher with the given name that executes the statements,
1181 // The description string documents what the matcher does, and is used
1186 // case we'll use the sequence of words in the matcher name as the
1210 // matcher name IsEven.
1216 // determined by the context in which you use the matcher and is
1218 // declaring it (nor can you). This allows the matcher to be
1228 // Sometimes you'll want to parameterize the matcher. For that you
1247 // Note that both the matcher description and its parameter are
1250 // In the matcher definition body, you can write 'foo_type' to
1262 // expression can reference all of the matcher's parameters and a
1264 // false, the expression should evaluate to the matcher's description;
1266 // the matcher. For example,
1286 // contain the sequence of words in the matcher name followed by the
1318 // 'arg_type' as that's determined by the context in which the matcher
1323 // While you can instantiate a matcher template with reference types,
1327 // matcher you will see the value of the referenced object but not its
1333 // Sometimes the matcher description alone isn't enough to explain why
1360 // When defining a new matcher, you should also consider implementing
1364 // the matcher parameters, which may leads to better compiler error
1365 // messages when the matcher is used wrong. They also allow