diff options
| author |  Abseil Team <absl-team@google.com> | 2024-03-26 12:04:23 -0700 |
|---|---|---|
| committer |  Copybara-Service <copybara-worker@google.com> | 2024-03-26 12:05:20 -0700 |
| commit | 68ce303da1920522a27e5d8e2732b3e50d3aae57 (patch) | |
| tree | cf3de5c2cad8c9530a209f6a0f9d69924b9074ce /absl/container/fixed_array_exception_safety_test.cc | |
| parent | e7858c73279d81cbc005d9c76a385ab535520635 (diff) | |
Respect `NDEBUG_SANITIZER`
Often code needs to know that it's built with sanitizers.
There are two common use for such information:
1. Work around incompatibility with sanitizers
2. Use sanitizers for more aggressive bug detection
With the current `ABSL_HAVE_*_SANITIZER` we can't distinguish
this two cased, and we didn't need that before.
Now user can define `NDEBUG_SANITIZER` to ask code like this
to avoid unnecessary checks.
I am not 100% sure that `NDEBUG` is not enough.
However relying on `NDEBUG` today will relax many tests, which
runs in NDEBUG mode only. So new `NDEBUG_SANITIZER` is safer
approach.
PiperOrigin-RevId: 619268413
Change-Id: I58185cd6886593a3742b8424deccdec366c2a35a
Diffstat (limited to 'absl/container/fixed_array_exception_safety_test.cc')
0 files changed, 0 insertions, 0 deletions