Skip to content
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

Disable compiler warnings by default #118

Merged
merged 1 commit into from
Feb 15, 2024
Merged

Disable compiler warnings by default #118

merged 1 commit into from
Feb 15, 2024

Conversation

ChrisThrasher
Copy link
Collaborator

@ChrisThrasher ChrisThrasher commented Feb 15, 2024

Unconditionally enabling -Werror is a heavy-handed approach and not ideal when shipping code to be used by many third parties. In fact it's even better to disable warnings by default since compiler warnings are not hard requirements. They're merely a development tool that developers should opt into.

Closes #117

Copy link

codecov bot commented Feb 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (cebc67c) 98.65% compared to head (18168f1) 98.65%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #118   +/-   ##
=======================================
  Coverage   98.65%   98.65%           
=======================================
  Files          11       11           
  Lines         223      223           
=======================================
  Hits          220      220           
  Misses          3        3           
Flag Coverage Δ
humble 98.65% <ø> (ø)
rolling 98.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ChrisThrasher ChrisThrasher changed the title Allow for disabling all compiler warnings Disable compiler warnings by default Feb 15, 2024
Unconditionally enabling -Werror is a heavy-handed approach and not
ideal when shipping code to be used by many third parties. In fact
it's even better to disable warnings by default since compiler
warnings are not hard requirements. They're merely a development
tool that developers should opt into.
@traversaro
Copy link

Great, this is even better for us!

@tylerjw tylerjw merged commit a6803dc into main Feb 15, 2024
35 checks passed
@delete-merged-branch delete-merged-branch bot deleted the warnings_option branch February 15, 2024 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants