This issue comes from cpplint#218 The Google C++ Style Guide states that Do not rely on transitive inclusions. This allows people to remove no-longer-needed #include statements from their headers without breaking clients. This also applies to related headers - foo.cc should include bar.h if it uses...

The new requires expression (since C++20) generates false positives e.g. concept Addable = requires(T x) { x + x; }; generates You don't need a ; after a } [readability/braces] [4] This repository publishes copies of Google's internal style guides to assist developers working on Google owned and o...

something wrong with function sys.stderr.write() when I use cpplint.py from [email protected]:google/styleguide.git the console always shows an Error msg: TypeError('write() argument must be str, not bytes') But if i use the cpplint.py from https://github.com/cpplint/cpplint everything goes well. By c...

I have read the instructions in the input field used to create this issue and I do realize that this request does in some ways violate that. But please consider this proposal anyway. So this style guide is intended for internal use at Google. That probably means it should not be distributed on Melpa...

The eclipse-java-google-style.xml specifies that javadoc should always be the "basic" format: The basic formatting of Javadoc blocks is as seen in this example: /** * Multiple lines of Javadoc text are written here, * wrapped normally... */ public int method(String p1) { ... } but that single-l...

As per the Java Style Guide: If there are both static and non-static imports, a single blank line separates the two blocks. But the eclipse-java-google-style.xml specifies a value of 0, when it should be 1. <setting id="org.eclipse.jdt.core.formatter.blank_lines_between_import_groups" value="0"...

The "Inputs and Outputs" section contains the following text Avoid defining functions that require a const reference parameter to outlive the call, because const reference parameters bind to temporaries. Instead, find a way to eliminate the lifetime requirement (for example, by copying the paramete...

This repository publishes copies of Google's internal style guides to assist developers working on Google owned and originated open source projects. Development on these guides does not take place here. Substantive changes to the style rules and suggested new rules should not be submitted as issues...

This repository publishes copies of Google's internal style guides to assist developers working on Google owned and originated open source projects. Development on these guides does not take place here. Substantive changes to the style rules and suggested new rules should not be submitted as issues...