-
Notifications
You must be signed in to change notification settings - Fork 285
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
Treat warnings as errors on release mode #1629
Conversation
aec144c
to
bba2391
Compare
Codecov Report
@@ Coverage Diff @@
## main #1629 +/- ##
=======================================
Coverage 58.92% 58.92%
=======================================
Files 477 477
Lines 40192 40192
=======================================
Hits 23685 23685
Misses 16507 16507
|
bba2391
to
81cc116
Compare
33d0f59
to
8896d7f
Compare
Just FYI, probably the "Treat warnings as errors on release mode" will need to be patched out in the version used in package managers of DART, as it is quite common that an older version of DART needs to be compiled with newer compilers, and this creates new warnings, that if use of |
@traversaro This makes sense to me. The motivation of this change was to prevent the case that the contributor and the CI don't fix the warnings by forgetting turnning on |
DART_TREAT_WARNINGS_AS_ERRORS
optionBefore creating a pull request
clang-format
Before merging a pull request
CHANGELOG.md