-
Notifications
You must be signed in to change notification settings - Fork 2
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
Initial clang-format file trying to respect seraphis standards #3
base: seraphis_wallet
Are you sure you want to change the base?
Initial clang-format file trying to respect seraphis standards #3
Conversation
…is_lib_hist_05_15_23 branch for commit history
We have page about such Seraphis wallet coding conventions in our wiki here. Can you please give a short list which conventions exactly this file enforces? The indentation by 4 blanks is obvious, as is all curly brackets on their own lines, but what else is there? E.g. is this meant to influence the formatting of comments somehow? |
@DangerousFreedom1984 : Please see my question from 3 weeks ago. And looking at this again, I asked myself whether this is something to really merge, and then having that file in the root (?) of the repository, or if the idea of this PR is just to make the file available to other parties that then pick it directly out of this PR. |
Sorry, this is not to merge. It is just an attempt to make the code here standardized. Since everyone has his own style of coding, would be nice if we enforced a written set of rules to (1) reduce overhead while writing and (2) have uniformity. The most important to me are:
|
e2ca1aa
to
bf95191
Compare
bf95191
to
e651e0b
Compare
Would it be useful to have a .clang-format file that does all the formatting job when you press Ctrl-Shift-I in VSCodium/VSCode? If so, this is the closest I got so far to mimic the non-standard Seraphis style.
For this to work you just have to place the .clang-format file in the root directory of your repo and have the clang extension.