Lines Matching refs:assertions

146 Libc++ contains a number of assertions whose goal is to catch undefined behavior in the
147 library, usually caused by precondition violations. Those assertions do not aim to be
149 In particular, these assertions do not change the complexity of algorithms. However, they
152 By default, these assertions are turned off. Vendors can decide to turn them on while building
154 When ``LIBCXX_ENABLE_ASSERTIONS`` is used, the compiled library will be built with assertions
155 enabled, **and** user code will be built with assertions enabled by default. If
157 assertions and the default when building user code will be to have assertions disabled.
158 As a user, you can consult your vendor to know whether assertions are enabled by default.
161 assertions are enabled in their code by defining ``_LIBCPP_ENABLE_ASSERTIONS=0|1`` before
163 compiler). Note that if the compiled library was built by the vendor without assertions,
164 functions compiled inside the static or shared library won't have assertions enabled even
166 where the static or shared library was compiled **with** assertions but the user tries to
218 Also note that the verbose termination function should never return. Since assertions in libc++