Skip to content

Commit a43a68f

Browse files
committed
Revert "more :"
This reverts commit be15769.
1 parent bf9d4c7 commit a43a68f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/csharp/tutorials/exploration/csharp-7.yml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ when inspecting the tuple using reflection at runtime, for example.
121121

122122
The examples above show the basic syntax to declare tuples. Tuples are
123123
most useful as return types for `private` and `internal` methods. Tuples
124-
provide a simple syntax for those methods to return multiple discrete values.
124+
provide a simple syntax for those methods to return multiple discrete values:
125125
You save the work of authoring a `class` or a `struct` that
126126
defines the type returned. There is no need to create a new type.
127127

@@ -140,13 +140,13 @@ when inspecting the tuple using reflection at runtime, for example.
140140

141141
The declaration for the method provides the names for the fields of the
142142
tuple that is returned. When you call the method, the return value is a
143-
tuple whose fields are `Max` and `Min`.
143+
tuple whose fields are `Max` and `Min`:
144144

145145
[!code-csharp[CallingTupleMethod](~/samples/snippets/csharp/new-in-7/program.cs#09_CallingTupleMethod "Calling a tuple returning method")]
146146

147147
There may be times when you want to unpackage the members of a tuple that
148148
were returned from a method. You can do that by declaring separate variables
149-
for each of the values in the tuple. This is called *deconstructing* the tuple.
149+
for each of the values in the tuple. This is called *deconstructing* the tuple:
150150

151151
[!code-csharp[CallingWithDeconstructor](~/samples/snippets/csharp/new-in-7/program.cs#10_CallingWithDeconstructor "Deconstructing a tuple")]
152152

@@ -155,11 +155,11 @@ when inspecting the tuple using reflection at runtime, for example.
155155
`Deconstruct` method provides a set of `out` arguments for each of the
156156
properties you want to extract. Consider
157157
this `Point` class that provides a deconstructor method that extracts
158-
the `X` and `Y` coordinates.
158+
the `X` and `Y` coordinates:
159159

160160
[!code-csharp[PointWithDeconstruction](~/samples/snippets/csharp/new-in-7/point.cs#11_PointWithDeconstruction "Point with deconstruction method")]
161161

162-
You can extract the individual fields by assigning a `Point` to a tuple.
162+
You can extract the individual fields by assigning a `Point` to a tuple:
163163

164164
[!code-csharp[DeconstructPoint](~/samples/snippets/csharp/new-in-7/program.cs#12_DeconstructPoint "Deconstruct a point")]
165165

@@ -176,7 +176,7 @@ when inspecting the tuple using reflection at runtime, for example.
176176
content: |
177177
Often when deconstructing a tuple or calling a method with `out` parameters, you're forced to define a variable whose value you don't care about and don't intend to use. C# adds support for *discards* to handle this scenario. A discard is a write-only variable whose name is `_` (the underscore character); you can assign all of the values that you intend to discard to the single variable. A discard is like an unassigned variable; apart from the assignment, the discard can't be used in code.
178178
179-
Discards are supported in the following scenarios.
179+
Discards are supported in the following scenarios:
180180
181181
* When deconstructing tuples or user-defined types.
182182

0 commit comments

Comments
 (0)