Skip to content

Commit dc35a53

Browse files
committed
Fix incorrect statement about ok()
Fixes #17676.
1 parent e2357cf commit dc35a53

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/doc/guide.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1678,11 +1678,11 @@ just `int`s.
16781678

16791679
Rust provides a method on these `IoResult<T>`s called `ok()`, which does the
16801680
same thing as our `match` statement, but assuming that we have a valid value.
1681-
If we don't, it will terminate our program. In this case, if we can't get
1682-
input, our program doesn't work, so we're okay with that. In most cases, we
1683-
would want to handle the error case explicitly. The result of `ok()` has a
1684-
method, `expect()`, which allows us to give an error message if this crash
1685-
happens.
1681+
We then call `expect()` on the result, which will terminate our program if we
1682+
don't have a valid value. In this case, if we can't get input, our program
1683+
doesn't work, so we're okay with that. In most cases, we would want to handle
1684+
the error case explicitly. `expect()` allows us to give an error message if
1685+
this crash happens.
16861686

16871687
We will cover the exact details of how all of this works later in the Guide.
16881688
For now, this gives you enough of a basic understanding to work with.

0 commit comments

Comments
 (0)