Skip to content

A
abseil-cpp
Commit 45eba9c1 by Abseil Team Committed by Copybara-Service
Options

Reformulate documentation of ABSL_LOCKS_EXCLUDED. 

The intent of the macro is to say what locks cannot be held when calling the method, not making a promise that they will be acquired.

PiperOrigin-RevId: 454158686
Change-Id: I71087460c3df27c7d6e0571156f19f525024f1de
parent db609075
Showing with 2 additions and 2 deletions
absl/base/thread_annotations.h
...@@ -154,8 +154,8 @@ ...@@ -154,8 +154,8 @@
// ABSL_LOCKS_EXCLUDED() // ABSL_LOCKS_EXCLUDED()
// //
// Documents the locks acquired in the body of the function. These locks // Documents the locks that cannot be held by callers of this function, as they
// cannot be held when calling this function (as Abseil's `Mutex` locks are // might be acquired by this function (Abseil's `Mutex` locks are
// non-reentrant). // non-reentrant).
#if ABSL_HAVE_ATTRIBUTE(locks_excluded) #if ABSL_HAVE_ATTRIBUTE(locks_excluded)
#define ABSL_LOCKS_EXCLUDED(...) __attribute__((locks_excluded(__VA_ARGS__))) #define ABSL_LOCKS_EXCLUDED(...) __attribute__((locks_excluded(__VA_ARGS__)))
......
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