Lines Matching +full:two +full:- +full:dimensional

4 `EXPECT_CALL()`, or use it to validate a value directly using two macros:
7 | :----------------------------------- | :------------------------------------ |
21 Built-in matchers (where `argument` is the function argument, e.g.
30 :-------------------------- | :-----------------------------------------------
37 | :--------------------- | :-------------------------------------------------- |
47 | `NotNull()`            | `argument` is a non-null pointer (raw or smart).    |
65 ## Floating-Point Matchers {#FpMatchers}
68 | :------------------------------- | :--------------------------------- |
69 …| `argument` is a `double` value approximately equal to `a_double`, treating two NaNs as unequal. |
70 …  | `argument` is a `float` value approximately equal to `a_float`, treating two NaNs as unequal. |
71 …` | `argument` is a `double` value approximately equal to `a_double`, treating two NaNs as equal. |
72 …`   | `argument` is a `float` value approximately equal to `a_float`, treating two NaNs as equal. |
73 | `IsNan()`   | `argument` is any floating-point type with a NaN value. |
75 The above matchers use ULP-based comparison (the same as used in googletest).
78 which requires comparing two NaNs for equality to return false. The
79 `NanSensitive*` version instead treats two NaNs as equal, which is often what a
83 | :------------------------------------------------ | :----------------------- |
84 …ble` value close to `a_double` (absolute error <= `max_abs_error`), treating two NaNs as unequal. |
85 …loat` value close to `a_float` (absolute error <= `max_abs_error`), treating two NaNs as unequal. |
86 …ouble` value close to `a_double` (absolute error <= `max_abs_error`), treating two NaNs as equal. |
87 …`float` value close to `a_float` (absolute error <= `max_abs_error`), treating two NaNs as equal. |
94 | :---------------------- | :------------------------------------------------- |
97 | `HasSubstr(string)`      | `argument` contains `string` as a sub-string.     |
105 … a base-64 escaped string whose unescaped string matches `m`.  The web-safe format from [RFC 4648]…
109 [here](../advanced.md#regular-expression-syntax). All of these matchers, except
114 Most STL-style containers support `==`, so you can use `Eq(expected_container)`
116 write the elements in-line, match them more flexibly, or get more informative
120 | :---------------------------------------- | :------------------------------- |
126 | `ElementsAre(e0, e1, ..., en)` | `argument` has `n + 1` elements, where the *i*-th element matche…
127 …lement values/matchers come from an initializer list, STL-style container, iterator range, or C-st…
131 …ainer`, and for all i, (the i-th element in `argument`, the i-th element in `container`) match `m`…
134 …lement values/matchers come from an initializer list, STL-style container, iterator range, or C-st…
145         int len)` -- see [Multi-argument Matchers](#MultiArgMatchers)).
146 *   The array being matched may be multi-dimensional (i.e. its elements can be
151     to compare two `Foo` containers where `Foo` doesn't support `operator==`,
165 | :------------------------------ | :----------------------------------------- |
166 | `Field(&class::field, m)`       | `argument.field` (or `argument->field` when `argument` is a pla…
167 | `Field(field_name, &class::field, m)` | The same as the two-parameter version, but provides a bet…
171 | `Property(&class::property, m)` | `argument.property()` (or `argument->property()` when `argument…
172 | `Property(property_name, &class::property, m)` | The same as the two-parameter version, but provi…
199 | :--------------- | :------------------------------------------------ |
201 | `ResultOf(result_description, f, m)` | The same as the two-parameter version, but provides a bett…
206 | :------------------------ | :---------------------------------------------- |
212 ## Multi-argument Matchers {#MultiArgMatchers}
214 Technically, all matchers match a *single* value. A "multi-argument" matcher is
219 :------ | :----------
231 | :------------------------- | :---------------------------------------------- |
233 | `Args<N1, N2, ..., Nk>(m)` | The tuple of the `k` selected (using 0-based indices) arguments matc…
240 | :------------------------------- | :-------------------------------------- |
242 …cept that the matchers come from an initializer list, STL-style container, iterator range, or C-st…
244 …cept that the matchers come from an initializer list, STL-style container, iterator range, or C-st…
251 | :---------------------- | :------------------------------------ |
262 | :---------------------------- | :------------------------------------------ |
270 | :----------------------------------- | :------------------------------------ |