You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If covering C++ style in terms of coding style is premature, a guide covering just code formatting is a fine start for this. Getting something in place where we can document decisions later as we make them is more important than answering every side case now. See https://github.com/Weasyl/weasyl/blob/master/STYLE_GUIDE.md for an example of a simple one I wrote for Weasyl.
Once done, add a new issue about finding a linter (e.g. http://clang.llvm.org/extra/clang-tidy/ looks promising but it may be a poor match for the project's infrastructure)
The text was updated successfully, but these errors were encountered:
It should go in the project top level. May just point to another existing style guide with caveats/deltas e.g. https://google.github.io/styleguide/cppguide.html
If covering C++ style in terms of coding style is premature, a guide covering just code formatting is a fine start for this. Getting something in place where we can document decisions later as we make them is more important than answering every side case now. See https://github.com/Weasyl/weasyl/blob/master/STYLE_GUIDE.md for an example of a simple one I wrote for Weasyl.
Once done, add a new issue about finding a linter (e.g. http://clang.llvm.org/extra/clang-tidy/ looks promising but it may be a poor match for the project's infrastructure)
The text was updated successfully, but these errors were encountered: