Skip to content

doc: Fix some typos in codying style #3056

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
+3 −3
Closed

doc: Fix some typos in codying style #3056

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions coding-style.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Think of the leading underscore as a shorthand for `this->`.
Template parameters use `CamelCase`
Note: because the Concept Technical Specification used CamelCase for concepts,
some Seastar concepts alse use CamelCase. These will be gradually deprecated
some Seastar concepts also use CamelCase. These will be gradually deprecated
and replaced with snake_case names. New concepts should use snake_case.
## Including header files
Expand Down Expand Up @@ -68,7 +68,7 @@ void a_function() {

An exception is namespaces -- the body is _not_ indented, to prevent files that are almost 100% whitespace left margin.

When making a change, if you need to insert an indentation level, you can temporarily break the rules by insering a half-indent, so that the patch is easily reviewable:
When making a change, if you need to insert an indentation level, you can temporarily break the rules by inserting a half-indent, so that the patch is easily reviewable:

```c++
void a_function() {
Expand Down Expand Up @@ -116,7 +116,7 @@ a_struct<T1, T2>::a_function(T3 a, T4 b) { // And I'm th

## Whitespace around operators

Whitespace around operators should match their precedence: high precedence = no spaces, low precedency = add spaces:
Whitespace around operators should match their precedence: high precedence = no spaces, low precedence = add spaces:

```c++
return *a + *b; // good
Expand Down