generic-library/googletest
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix typos discovered by codespell

Browse Source
This commit is contained in:
Christian Clauss 2021-09-16 21:44:29 +02:00 committed by GitHub
parent 861a75ed5d
commit 5b43f14be9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/gmock_cook_book.md
View File

@ -1452,7 +1452,7 @@ the pointer is copied. When the last matcher that references the implementation
object dies, the implementation object will be deleted. object dies, the implementation object will be deleted.
Therefore, if you have some complex matcher that you want to use again and Therefore, if you have some complex matcher that you want to use again and
again, there is no need to build it everytime. Just assign it to a matcher again, there is no need to build it every time. Just assign it to a matcher
variable and use that variable repeatedly! For example, variable and use that variable repeatedly! For example,
```cpp ```cpp
@ -2601,7 +2601,7 @@ efficient. When the last action that references the implementation object dies,
the implementation object will be deleted. the implementation object will be deleted.
If you have some complex action that you want to use again and again, you may If you have some complex action that you want to use again and again, you may
not have to build it from scratch everytime. If the action doesn't have an not have to build it from scratch every time. If the action doesn't have an
internal state (i.e. if it always does the same thing no matter how many times internal state (i.e. if it always does the same thing no matter how many times
it has been called), you can assign it to an action variable and use that it has been called), you can assign it to an action variable and use that
variable repeatedly. For example: variable repeatedly. For example:
@ -4188,7 +4188,7 @@ This implementation class does *not* need to inherit from any particular class.
What matters is that it must have a `Perform()` method template. This method What matters is that it must have a `Perform()` method template. This method
template takes the mock function's arguments as a tuple in a **single** template takes the mock function's arguments as a tuple in a **single**
argument, and returns the result of the action. It can be either `const` or not, argument, and returns the result of the action. It can be either `const` or not,
but must be invokable with exactly one template argument, which is the result but must be invocable with exactly one template argument, which is the result
type. In other words, you must be able to call `Perform<R>(args)` where `R` is type. In other words, you must be able to call `Perform<R>(args)` where `R` is
the mock function's return type and `args` is its arguments in a tuple. the mock function's return type and `args` is its arguments in a tuple.