Skip to content

Commit 92b2190

Browse files
authored
Merge pull request #29006 from cruisediary/master
2 parents dee82db + 3fda905 commit 92b2190

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/TypeChecker.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -370,12 +370,12 @@ guesswork. However, we note that the type of an enum member actually
370370
has a regular structure. For example, consider the ``Optional`` type::
371371

372372
enum Optional<T> {
373-
case None
374-
case Some(T)
373+
case none
374+
case some(T)
375375
}
376376

377-
The type of ``Optional<T>.None`` is ``Optional<T>``, while the type of
378-
``Optional<T>.Some`` is ``(T) -> Optional<T>``. In fact, the
377+
The type of ``Optional<T>.none`` is ``Optional<T>``, while the type of
378+
``Optional<T>.some`` is ``(T) -> Optional<T>``. In fact, the
379379
type of an enum element can have one of two forms: it can be ``T0``,
380380
for an enum element that has no extra data, or it can be ``T2 -> T0``,
381381
where ``T2`` is the data associated with the enum element. For the

0 commit comments

Comments
 (0)