Skip to content

Update Guidelines(8th Edition).xml #184

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

Merged
merged 1 commit into from
Jul 28, 2021
Merged

Update Guidelines(8th Edition).xml #184

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
3 changes: 1 addition & 2 deletions docs/Guidelines(8th Edition).xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -203,7 +203,6 @@
<guideline key="Ch06_95f0537" severity="DO" section="Coding" subsection="Properties">DO implement non-nullable reference-type automatically implemented properties as read-only.</guideline>
<guideline key="Ch06_b85aa4e" severity="DO" section="Coding" subsection="Properties">DO assign non-nullable reference-type properties before instantiation completes.</guideline>
<guideline key="Ch06_759b766" severity="DO" section="Coding" subsection="Properties">"DO implement non-nullable read/write reference fully implemented properties with a nullable backing field, a null-forgiveness operator when returning the field from the getter, and non-null validation in the property setter."</guideline>
<guideline key="Ch06_34774e8" severity="DO" section="Coding" subsection="Properties">"DO allow properties to be set in any order, even if this results in a temporarily invalid object state."</guideline>
<guideline key="Ch04_2dc14f6" severity="DO" section="Coding" subsection="Strings">DO favor composite formatting over use of the addition operator for concatenating strings when localization is a possibility.</guideline>
<guideline key="Ch09_6d059d3" severity="DO NOT" section="Coding" subsection="Structs">"DO NOT define a struct unless it logically represents a single value, consumes 16 bytes or less of storage, is immutable, and is infrequently boxed."</guideline>
<guideline key="Ch09_be07b3a" severity="DO" section="Coding" subsection="Structs">DO ensure that the default value of a struct is valid; encapsulation cannot prevent obtaining the default “all zero” value of a struct.</guideline>
Expand Down Expand Up @@ -250,4 +249,4 @@
<guideline severity="CONSIDER" section="Coding" subsection="Variables">CONSIDER using target-typed new expressions any time that the instance clearly shows its type.</guideline>
<guideline key="Ch04_9fa9f67" severity="AVOID" section="Coding" subsection="Whitespace">"AVOID omitting braces, except for the simplest of single-line if statements."</guideline>
<guideline key="Ch04_19bd2d2" severity="DO" section="Coding" subsection="Whitespace">"DO use parentheses to make code more readable, particularly if the operator precedence is not clear to the casual reader."</guideline>
</Guidelines>
</Guidelines>