-
Notifications
You must be signed in to change notification settings - Fork 627
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
Warning flags #20
Comments
Good idea. But how should we handle this in tutorials? Should we direct the reader to add this flag during project setup, or should we just do it while developing the project behind the scenes? |
We can mention it as the recommended setting as a tip to readers, and ask authors to add it to sample/final projects attached to tutorials. I wouldn't want to mention it every time if a tutorial is a "start a project from scratch" type. |
I don't believe warning flags belong in a style guide, as they don't pertain to style and have no direct impact on formatting. IMO these belong more in a 'Best Practices' type guide. |
I agree with @micpringle regarding 'Best Practices'. +1 for not including this in the style guide. |
Good point, yeah it does make sense to put this guideline in a best practices guide instead of a style guide. Maybe we can just put it on the tutorial team guide somewhere. |
What are good warning flags to enable by default?
I prefer -Wall -Wextra -Wno-unused-parameter. It might be good to have these as suggested settings.
The text was updated successfully, but these errors were encountered: