coffee/googletest
1
0
Fork 0
mirror of https://github.com/google/googletest.git synced 2026-04-30 19:09:20 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge fac82b687b4910e551431d83613859e9a2c7eef8 into d72f9c8aea6817cdf1ca0ac10887f328de7f3da2

Browse Source
This commit is contained in:
Jack Lau 2026-04-06 10:08:02 -04:00 committed by GitHub
commit aa2d152479
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/faq.md
View File

@ -325,7 +325,7 @@ You may still want to use `SetUp()/TearDown()` in the following cases:
enabled in the compiler. Therefore you should prefer `TearDown()` if you
want to write portable tests that work with or without exceptions.
* The GoogleTest team is considering making the assertion macros throw on
platforms where exceptions are enabled (e.g. Windows, Mac OS, and Linux
platforms where exceptions are enabled (e.g. Windows, macOS, and Linux
client-side), which will eliminate the need for the user to propagate
failures from a subroutine to its caller. Therefore, you shouldn't use
GoogleTest assertions in a destructor if your code could run on such a