Skip to content

Remove outdated return type restriction from match documentation #642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RadotJar wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Remove outdated return type restriction from match documentation #642

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -459,10 +459,9 @@ class Result<T, E> {
}
```

`match` is like chaining `map` and `mapErr`, with the distinction that with `match` both functions must have the same return type.
The differences between `match` and chaining `map` and `mapErr` are that:
- with `match` both functions must have the same return type `A`
- `match` unwraps the `Result<T, E>` into an `A` (the match functions' return type)
`match` is like chaining `map` and `mapErr`.
The difference between `match` and chaining `map` and `mapErr` is that:
- `match` unwraps the `Result<T, E>` into an `A | B` (either the return type of the match function's ok callback, or the return type of the match function's error callback)
- This makes no difference if you are performing side effects only

**Example:**
Expand Down