Global
/
googletest
mirror of https://github.com/google/googletest.git
1
0
Fork 0
Code Activity

Merge fac82b687b into 283c17563f

This commit is contained in:
Jack Lau 2026-09-03 19:28:14 +02:00 committed by GitHub
parent 283c17563f fac82b687b
commit 74347ff1ea
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