-
Notifications
You must be signed in to change notification settings - Fork 7
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
Select coding conventions & auto formatting #46
Comments
Auto formatting will be handled by clang-format. |
It seems better to unify intent char to 4 spaces. |
I'll check it out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you see the codes as raw text, it has mixed tabs and spaces.
Also, comments are written in
/* */
and//
.(FYI, the
/* */
is basic commenting notation in old C standard,//
were back-ported from C++ standard)I don't want to force use
/* */
for all the comments, but it may be effective by setting each commenting notation into its specific meaning.ex. use
/* */
for documentation formatting comments, use//
for general comments in code blocks.Maybe there would be some other things to consider for standard coding conventions in this project.
After selecting coding conventions, auto-formatting and style check automation may be required. It will improve PR review (not arguing with minor coding styles, reducing meaningless formatting commits)
Anyone who has some opinions about coding conventions, please write your opinions here.
The text was updated successfully, but these errors were encountered: