-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Another cleanup round in main #2163
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2163 +/- ##
==========================================
+ Coverage 62.65% 63.25% +0.59%
==========================================
Files 97 98 +1
Lines 19721 19581 -140
Branches 9710 9552 -158
==========================================
+ Hits 12357 12386 +29
+ Misses 5132 5122 -10
+ Partials 2232 2073 -159
Continue to review full report at Codecov.
|
I like the removal of asserts. Pointless especially with smart pointer usages. std::copy_n can also help with removal of some memcpy usages. |
There are still some CI jobs failing for Windows x86. I'll try to fix those issues during the day. |
@neheb I merged without requesting your re-approval, since I just had to fix some casting warnings. |
This is another round of cleanups I applied to the codebase. Each commit has different topics and is self-isolated. The commits that could raise more discussions are:
EXIT_SUCCESS
&EXIT_FAILURE
. I always use these in my projects as I think they make the code more readable.assert
. I have a strong positioning against the usage of assert in production code, as such code would only be relevant in debug builds. Any check that is worth to be added in production should be present in all kind of builds, and for that we haveenforce
in our codebase. Specially ugly were theassert(false);
statements ... those ones simply highlight that certain paths of the code can be considered as "dead-code". If at any point we would add a test covering those areas, the tests would simply fail in debug mode.