Lines Matching refs:asserts

11 a crash if the condition is not met. Consistent use of asserts is one aspect of
61   most asserts ``CHECK`` rather than ``DCHECK``, unless there is a critical
75   Use ``PW_ASSERT`` from ``pw_assert/assert.h`` for asserts in headers or
345     This also asserts that ``abs_tolerance >= 0``.
406    asserts, due to differing module choices.
410 4. ``PW_CHECK_*`` can trigger circular dependencies when asserts are used from
436       // want rich asserts or logs, move the function into the .cc file, and
568 In theory, ``DCHECK_*`` macros should never be used and all the asserts should
591 - **Prefer to use DCHECK_* variants for internal asserts** that attempt to
633 1. **C compatibility** - Since asserts are typically invoked from arbitrary
637 2. **Capturing both expressions and values** - Since asserts can trigger in
639    information to help identifying the root cause of the fault. For asserts,
649    handling of asserts. In some cases, an assert might trigger printing out
654 particular, the need to support tokenized asserts and the need to support
662 The problem with asserts like ``PW_CHECK_LE(a, b)`` instead of
699   advised approach to get **tokenized asserts**--by using tokenized logging,
702 Note: If one desires a null assert module (where asserts are removed), use
703 ``pw_assert_log`` in combination with ``pw_log_null``. This will direct asserts