We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Per this issue: google/styleguide#408
Consider the fork at https://github.com/cpplint/cpplint (also published to Pypi) if you feel like contributing.
\cc @jwnimmer-tri @jamiesnape
The text was updated successfully, but these errors were encountered:
Don't think I agree. We already fork ourselves, so it is not buying us anything.
Sorry, something went wrong.
Yes, it may have additional overhead of configurations changing, but it may have improvements codewise that we may want at some point.
I'd call this closeable if we at least put a comment at the top of our forked cpplint pointing to the new stuff.
Sounds a little strange. I don't we should be deviating too much anyway unless the Google version is broken, whether to not there are improvements.
Aye. Will close then.
EricCousineau-TRI
No branches or pull requests
Per this issue: google/styleguide#408
\cc @jwnimmer-tri @jamiesnape
The text was updated successfully, but these errors were encountered: