Fix a style guide oversight #682
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -34,6 +34,7 @@ Following this guide and formatting your code as detailed will likely get your p | |||
| - The opening brace for namespaces, classes, functions, enums, structs, unions, conditionals, and loops go on the next line. | |||
| - With array initializer lists and lambda expressions it is OK to keep the brace on the same line. | |||
| - References and pointers have the ampersand or asterisk against the type name, not the variable name. Example: `int* var`, not `int *var`. | |||
| - Don't use multi-line comments (`/* Comment text */`) use single-line comments (`// Comment text`) instead. | |||
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Fixes an oversight which says to not use mult-line comments.
|
lgtm ;) |
|
lgtm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Fixes an oversight which says to not use mult-line comments.
Thanks @BhaaLseN for pointing this out.