Read-only mirrors. Development, issues and pull requests are on GitHub.

summaryrefslogtreecommitdiffhomepage
path: root/docs/thread-safety.md
diff options
context:
space:
mode:
authorMartin Hořeňovský2025-08-25 21:27:29 +0200
committerMartin Hořeňovský2025-08-25 21:30:21 +0200
commit25319fd3047c6bdcf3c0170e76fa526c77f99ca9 (patch)
tree80513aed065a4bb3f97af1868b0a307215d350b9 /docs/thread-safety.md
parent85c4bad86b0bd29b6d2f5aa270401c0a642d53b1 (diff)
downloadcatch3-3.10.0.tar.gz
v3.10.0v3.10.0
Diffstat (limited to 'docs/thread-safety.md')
-rw-r--r--docs/thread-safety.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/thread-safety.md b/docs/thread-safety.md
index 3d48eb0b..e0092ded 100644
--- a/docs/thread-safety.md
+++ b/docs/thread-safety.md
@@ -44,6 +44,8 @@ they are assertion macro + an if).
## Assertion-like message macros and spawned threads
+> Assertion-like messages were made thread safe in Catch2 3.10.0
+
Similarly to assertion macros, not all assertion-like message macros can
be used from spawned thread.
@@ -55,6 +57,8 @@ thus can be used from any thread.
## Message macros and spawned threads
+> Message macros were made thread safe in Catch2 3.10.0
+
Macros that add extra messages to following assertion, such as `INFO`
or `CAPTURE`, are all thread safe and can be used in any thread. Note
that these messages are per-thread, and thus `INFO` inside a user-spawned