This style guide helps developers set up their initial environment.
Therefore, I think it has a great influence on beginner users.
So I think It need to respond to l10n.
Any plans for the l10n?
@pwnall
I'm reading: https://github.com/google/styleguide/blob/gh-pages/cppguide.html
esp about the multiple inheritance part.
And I just want to let you know: the diamond problem is solved! please check here:
https://github.com/joortcom/DDIFI
The diamond problem solved! Using virtual property to de...
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...
C system headers (more precisely: headers in angle brackets with the .h extension), e.g., <unistd.h>, <stdlib.h>.
the clarification actually makes things worse - any file can be included via angle brackets, all they do is tell the compiler to search in some predefined path, rather than...
After go.1.18 you can use any and interface{} are interchangeably.
I would love the change so when I do a ctrl+F and look for styles around how interfaces should work I don't get false positives.
The style guide already prefers the use.
I would just want the examples here updated
https://google.git...