You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building LLVM for example, many files include <cassert>, resulting in lots of include churn relating to this header which can be mitigated with an include guard.
Is there a technical reason for the missing include guard for cassert?
This is by design. <cassert> and <assert.h> shouldn't have include guard themselves in order to satisfy the requirements in [assertions.assert]/4 and the corresponding requirements in C.
When building LLVM for example, many files include
<cassert>
, resulting in lots of include churn relating to this header which can be mitigated with an include guard.Is there a technical reason for the missing include guard for
cassert
?STL/stl/inc/cassert
Lines 5 to 7 in 63354c3
The text was updated successfully, but these errors were encountered: