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

clear up some additional Wshadow warnings on older compilers #232

Merged
merged 4 commits into from
Feb 20, 2019

Conversation

phlptp
Copy link
Collaborator

@phlptp phlptp commented Feb 20, 2019

This PR adds Wshadow flag and clears up some warnings

@codecov
Copy link

codecov bot commented Feb 20, 2019

Codecov Report

Merging #232 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #232   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          12     12           
  Lines        2087   2093    +6     
=====================================
+ Hits         2087   2093    +6
Impacted Files Coverage Δ
include/CLI/Option.hpp 100% <100%> (ø) ⬆️
include/CLI/App.hpp 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 17d05b0...804c239. Read the comment docs.

@henryiii
Copy link
Collaborator

So that's why you've been renaming those. Okay.

@phlptp
Copy link
Collaborator Author

phlptp commented Feb 20, 2019

I kept getting a large number of warnings when trying to use CLI11 in some projects. I think most of the warnings on older gcc are mostly false positives but Wshadow has saved me a few times with the newer ones, so I like to leave it on.

@henryiii henryiii merged commit 546d5ec into CLIUtils:master Feb 20, 2019
@henryiii
Copy link
Collaborator

Looks good! Thanks!

@phlptp phlptp deleted the Wshadow-warnings branch February 21, 2019 15:48
@henryiii henryiii added this to the v1.8 milestone Feb 28, 2019
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.

2 participants