[PATCH] D76622: [analyzer] ConstraintManager - use EXPENSIVE_CHECKS instead of (gcc specific) __OPTIMIZE__ guard

[Simon Pilgrim via Phabricator via cfe-commits]

RKSimon added a comment.

In D76622#1938009 <https://reviews.llvm.org/D76622#1938009>, @NoQ wrote:

> Sounds good but eventually i hope we re-enable this assert in release+assert builds (D57062 <https://reviews.llvm.org/D57062>).


SGTM as long as you don't reintroduce a compiler specific guard


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D76622/new/

https://reviews.llvm.org/D76622