As a fly-by fix, enable the complexity-changing assertions in __debug_less
only when the full debug mode is enabled, since debugging level 0 is usually
understood to only contain basic assertions that do not change the complexity
of algorithms.
Details
Details
- Reviewers
 jdoerfert ldionne - Group Reviewers
 Restricted Project - Commits
 - rG95c0f2d115e2: [libc++] Remove workarounds for re-defining _LIBCPP_ASSERT in the test suite
 
Diff Detail
Diff Detail
- Repository
 - rG LLVM Github Monorepo
 
Event Timeline
| libcxx/test/libcxx/algorithms/debug_less.pass.cpp | ||
|---|---|---|
| 8–24 | I recommend more like this. (And likewise throughout.)  | |
Comment Actions
CI passed after retrying the job that had failed due to a flake.
Landing this since this is now an uncontroversial workaround removal -- this is not built on top of the projected new assertion handler work.
I recommend more like this. (And likewise throughout.)