Search results

Investigate dangling reference issues due to unexpected expression template usage

Status: Open.

#162 In jeremy-rifkin/libassert;

· jeremy-rifkin opened on Jul 8, 2026

Install rules are always enabled for downstream consumers

Status: Open.

#158 In jeremy-rifkin/libassert;

· wopss opened on Jan 21, 2026

ASSERT_VAL in member initializer of constexpr constructor causes ICE on GCC

upstream

Status: Open.

#157 In jeremy-rifkin/libassert;

· CrackedMatter opened on Nov 17, 2025

Custom failure handler on Windows causes assert in DEBUG and undefined behavior in Release

Status: Open.

#154 In jeremy-rifkin/libassert;

· wopss opened on Sep 25, 2025

Fails to build due to macro redefinition in libdwarf

upstream

Status: Open.

#146 In jeremy-rifkin/libassert;

· OpenByteDev opened on Jul 2, 2025

Integration with other test frameworks

resolved in next release

Status: Open.

#124 In jeremy-rifkin/libassert;

· ThibaultLemaire opened on Feb 27, 2025

ASSERT or variant returning result of the expression (not just left-hand operand)

enhancementNew feature or requestNew feature or request

Status: Open.

#101 In jeremy-rifkin/libassert;

· NyanSten opened on Aug 22, 2024

Unconditional assertion that does not cause [[noreturn]]

enhancementNew feature or requestNew feature or request

Status: Open.

#100 In jeremy-rifkin/libassert;

· NyanSten opened on Aug 22, 2024

Do you think it'd be possible to integrate the ASSERT() expressions with C++ contracts?

c++26

enhancementNew feature or requestNew feature or request

Status: Open.

#37 In jeremy-rifkin/libassert;

· GavinRay97 opened on Dec 10, 2022