You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ then open a pull request. :zap:
25
25
26
26
Use `let foo = …` over `var foo = …` wherever possible (and when in doubt). Only use `var` if you absolutely have to (i.e. you *know* that the value might change, e.g. when using the `weak` storage modifier).
27
27
28
-
_Rationale:_ The intent and meaning of both keywords is clear, but *let-by-default* results in safer and clearer code.
28
+
_Rationale:_ The intent and meaning of both keywords are clear, but *let-by-default* results in safer and clearer code.
29
29
30
30
A `let`-binding guarantees and *clearly signals to the programmer* that its value will never change. Subsequent code can thus make stronger assumptions about its usage.
31
31
@@ -117,7 +117,7 @@ subscript(index: Int) -> T {
117
117
}
118
118
```
119
119
120
-
_Rationale:_ The intent and meaning of the first version is clear, and results in less code.
120
+
_Rationale:_ The intent and meaning of the first version are clear, and results in less code.
121
121
122
122
#### Always specify access control explicitly for top-level definitions
0 commit comments