Contributing: fix typos (#3125)
This commit is contained in:
parent
6f24703c82
commit
02b535d712
|
@ -274,7 +274,7 @@ A value-semantics class like the above would be automatically generated by a "re
|
||||||
class Point(int X, int Y);
|
class Point(int X, int Y);
|
||||||
```
|
```
|
||||||
|
|
||||||
By default, this would generate all of the above, except parameter names would be upper case. If you want to supercede default behavior, you can give it a body and do that explicitly. For instance, you could make X mutable:
|
By default, this would generate all of the above, except parameter names would be upper case. If you want to supersede default behavior, you can give it a body and do that explicitly. For instance, you could make X mutable:
|
||||||
|
|
||||||
``` c#
|
``` c#
|
||||||
class Point(int X, int Y)
|
class Point(int X, int Y)
|
||||||
|
|
|
@ -13,7 +13,7 @@
|
||||||
|
|
||||||
The way `base.` works in classes, if the base implementation that was present at compile
|
The way `base.` works in classes, if the base implementation that was present at compile
|
||||||
time is removed at rune time, the CLR will search for the next implementation in the
|
time is removed at rune time, the CLR will search for the next implementation in the
|
||||||
heirarchy and use that instead. For example,
|
hierarchy and use that instead. For example,
|
||||||
|
|
||||||
```C#
|
```C#
|
||||||
class A
|
class A
|
||||||
|
|
|
@ -25,7 +25,7 @@ This is the next major release (as C# 8.0 is a done deal at this point). Putting
|
||||||
|
|
||||||
## #146
|
## #146
|
||||||
|
|
||||||
There's something to this, but instead of marking seperately, we think it is paired with allowing nullary constructors on structs . For those we would warn on uses of `default(S)` that we can detect, similar to nullability.
|
There's something to this, but instead of marking separately, we think it is paired with allowing nullary constructors on structs . For those we would warn on uses of `default(S)` that we can detect, similar to nullability.
|
||||||
|
|
||||||
## #812
|
## #812
|
||||||
|
|
||||||
|
|
|
@ -168,7 +168,7 @@ Consider `IAsyncEnumerable<int> GetData([EnumeratorCancellation] CancellationTok
|
||||||
The implementer of this method can simply use the parameter in the method body.
|
The implementer of this method can simply use the parameter in the method body.
|
||||||
The consumer can use either consumption patterns above:
|
The consumer can use either consumption patterns above:
|
||||||
1. if you use `GetData(token)`, then the token is saved into the async-enumerable and will be used in iteration,
|
1. if you use `GetData(token)`, then the token is saved into the async-enumerable and will be used in iteration,
|
||||||
2. if you use `givenIAsyncEnumerable.WithCancellation(token)`, then the token passed to `GetAsyncEnumerator` will supercede any token saved in the async-enumerable.
|
2. if you use `givenIAsyncEnumerable.WithCancellation(token)`, then the token passed to `GetAsyncEnumerator` will supersede any token saved in the async-enumerable.
|
||||||
|
|
||||||
## foreach
|
## foreach
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue