You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the code, I can see some identifiers aren't using the absl namespace.
I'm mostly thinking about some defines/macros, not C++ classes/functions.
For example, there is:
LOCKABLE
ANNOTATE_CONTIGUOUS_CONTAINER
DYNAMIC_ANNOTATIONS_ENABLED
Is it a bug or a feature?
Personally, I would expect ABSL_LOCKABLE instead of LOCKABLE.
The text was updated successfully, but these errors were encountered:
They are not prefixed with ABSL_ intentionally. Respectively:
LOCKABLE: We use the naming in https://clang.llvm.org/docs/ThreadSafetyAnalysis.html. We don't expect this macro to have any definition conflict with other macros. Let me guess, are you having problem with a enum named LOCKABLE?
ANNOTATE_CONTIGUOUS_CONTAINER: These are widely-adopted ASAN macros that we don't want to rename.
DYNAMIC_ANNOTATIONS_ENABLED: This is a build switch to enable dynamic annotations. We don't think it's necessary to rename it, because if user has -DDYNAMIC_ANNOTATIONS_ENABLED they probably want -DABSL_DYNAMIC_ANNOTATIONS_ENABLED too.
Looking at the code, I can see some identifiers aren't using the absl namespace.
I'm mostly thinking about some defines/macros, not C++ classes/functions.
For example, there is:
Is it a bug or a feature?
Personally, I would expect ABSL_LOCKABLE instead of LOCKABLE.
The text was updated successfully, but these errors were encountered: