In PR #81, rather than completely removing assertions in the code, this including a no-op function such that the condition is still evaluated, but not acted upon. This was done because there are a few instances where a value was computed and used only for the assert, and no other reason. If the assert is removed, then the value becomes unused and is flagged as such (i.e. compiler warning).
The fix in #81 was only an interim in order to get the code to compile and run. The preferred fix would be to identify cases where a value is computed and only used in an assert, and remove them. This is likely just a matter of removing the no-op function and fixing the warnings that come up.
In PR #81, rather than completely removing assertions in the code, this including a no-op function such that the condition is still evaluated, but not acted upon. This was done because there are a few instances where a value was computed and used only for the assert, and no other reason. If the assert is removed, then the value becomes unused and is flagged as such (i.e. compiler warning).
The fix in #81 was only an interim in order to get the code to compile and run. The preferred fix would be to identify cases where a value is computed and only used in an assert, and remove them. This is likely just a matter of removing the no-op function and fixing the warnings that come up.