Skip to content

GitLab

"googlemock/vscode:/vscode.git/clone" did not exist on "b138afde15fff4b81afd926a7bdfb70928358b56"
Commit cfb5ef4e authored by Abseil Team's avatar Abseil Team Committed by vslashg
Browse files

Googletest export 

Remove public buganizer reference from googletest cookbook.

It also seems that this bug is obsolete.

PiperOrigin-RevId: 298598298
parent e588eb1f
Show whitespace changes
Inline Side-by-side
Showing with 1 addition and 1 deletion
googlemock/docs/cook_book.md
View file @ cfb5ef4e
...@@ -421,7 +421,7 @@ sadly they are side effects of C++'s limitations): ...@@ -421,7 +421,7 @@ sadly they are side effects of C++'s limitations):
`NiceMock<StrictMock<MockFoo> >`) is **not** supported. `NiceMock<StrictMock<MockFoo> >`) is **not** supported.
2. `NiceMock<MockFoo>` and `StrictMock<MockFoo>` may not work correctly if the 2. `NiceMock<MockFoo>` and `StrictMock<MockFoo>` may not work correctly if the
destructor of `MockFoo` is not virtual. We would like to fix this, but it destructor of `MockFoo` is not virtual. We would like to fix this, but it
requires cleaning up existing tests. http://b/28934720 tracks the issue. requires cleaning up existing tests.
3. During the constructor or destructor of `MockFoo`, the mock object is *not* 3. During the constructor or destructor of `MockFoo`, the mock object is *not*
nice or strict. This may cause surprises if the constructor or destructor nice or strict. This may cause surprises if the constructor or destructor
calls a mock method on `this` object. (This behavior, however, is consistent calls a mock method on `this` object. (This behavior, however, is consistent
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment