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
HPX should not put -DNDEBUG into its hpx_application.pc. The choice of using -DNDEBUG or not should belong to the application, not a library (HPX) that an application uses. It is often very convenient to be able to use assert() to track down bugs, even in production code. -DNDEBUG prevents this, forcing people to roll their own assert statement.
Since HPX already uses HPX_ASSERT, why does it care about -DNDEBUG? This seems like an overzealous optimization to me; HPX_DISABLE_ASSERTS should suffice.
The text was updated successfully, but these errors were encountered:
HPX should not put -DNDEBUG into its hpx_application.pc. The choice of using -DNDEBUG or not should belong to the application, not a library (HPX) that an application uses. It is often very convenient to be able to use assert() to track down bugs, even in production code. -DNDEBUG prevents this, forcing people to roll their own assert statement.
Since HPX already uses HPX_ASSERT, why does it care about -DNDEBUG? This seems like an overzealous optimization to me; HPX_DISABLE_ASSERTS should suffice.
The text was updated successfully, but these errors were encountered: