Create an additional level of assertions that would always be active where performance costs are low
SMijin opened this issue · 1 comments
SMijin commented
Most errors in ReMKiT1D config files can be caught using our assertion system. However, this is currently only active in debug mode, which both makes it inconvenient for regular users, as well as exposing them to potential issues with debug mode (see for example issue #10 ).
The proposed solution is to implement an additional level of assertions in the code, which should enable most startup assertions to run without impacting performance-critical sections of the code (like derivation calls or matrix solves).