diff options
author | QMK Bot <hello@qmk.fm> | 2023-06-21 02:58:50 +0000 |
---|---|---|
committer | QMK Bot <hello@qmk.fm> | 2023-06-21 02:58:50 +0000 |
commit | 63735431d3e35ae6bd39df064ec42ed4cc9ecf40 (patch) | |
tree | 39d8f8e076ef5134cb805cd9a7f0db5b9f4ceadb | |
parent | dad41bd2f67f76dbaaa958dff043fe0a9ba19359 (diff) | |
parent | 2f1cac6e9febd6209ff9a012b7fcd03af4f9cb82 (diff) |
Merge remote-tracking branch 'origin/master' into develop
-rw-r--r-- | docs/coding_conventions_c.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/coding_conventions_c.md b/docs/coding_conventions_c.md index 3f44da713d..32f6de7ff7 100644 --- a/docs/coding_conventions_c.md +++ b/docs/coding_conventions_c.md @@ -8,8 +8,8 @@ Most of our style is pretty easy to pick up on, but right now it's not entirely * Closing Brace: Lined up with the first character of the statement that opens the block * Else If: Place the closing brace at the beginning of the line and the next opening brace at the end of the same line. * Optional Braces: Always include optional braces. - * Good: if (condition) { return false; } - * Bad: if (condition) return false; + * Good: `if (condition) { return false; }` + * Bad: `if (condition) return false;` * We encourage use of C style comments: `/* */` * Think of them as a story describing the feature * Use them liberally to explain why particular decisions were made. |