summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAbseil Team <absl-team@google.com>2021-04-06 12:22:23 -0700
committerDino Radaković <dinor@google.com>2021-04-07 23:39:10 -0700
commit54689b19356af73978af605ef5c4e2b090ef9d2b (patch)
treef29434168d9fe86bec80487d641a62afbcfefd40
parent5c8ca58edfb304b2dd5e6061f83387470826dd87 (diff)
downloadgoogletest-54689b19356af73978af605ef5c4e2b090ef9d2b.tar.gz
googletest-54689b19356af73978af605ef5c4e2b090ef9d2b.zip
Googletest export
Docs: Clarifying matcher in `Pointwise` and `UnorderedPointwise` PiperOrigin-RevId: 367059198
-rw-r--r--docs/gmock_cheat_sheet.md9
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/gmock_cheat_sheet.md b/docs/gmock_cheat_sheet.md
index 1e6b44ef..ddc17cc5 100644
--- a/docs/gmock_cheat_sheet.md
+++ b/docs/gmock_cheat_sheet.md
@@ -362,10 +362,11 @@ messages, you can use:
int len)` -- see [Multi-argument Matchers](#MultiArgMatchers)).
* The array being matched may be multi-dimensional (i.e. its elements can be
arrays).
-* `m` in `Pointwise(m, ...)` should be a matcher for `::std::tuple<T, U>`
- where `T` and `U` are the element type of the actual container and the
- expected container, respectively. For example, to compare two `Foo`
- containers where `Foo` doesn't support `operator==`, one might write:
+* `m` in `Pointwise(m, ...)` and `UnorderedPointwise(m, ...)` should be a
+ matcher for `::std::tuple<T, U>` where `T` and `U` are the element type of
+ the actual container and the expected container, respectively. For example,
+ to compare two `Foo` containers where `Foo` doesn't support `operator==`,
+ one might write:
```cpp
using ::std::get;
OpenPOWER on IntegriCloud