Skip to content

Fixed typo : failable -> fallible #177

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.

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

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
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
6 changes: 3 additions & 3 deletions docs/ErrorHandling.rst
Original file line number Diff line number Diff line change
Expand Up @@ -570,11 +570,11 @@ the NSError back like they do today, and have to throw the result
manually.

For initializers, importing an initializer as throwing takes
precedence over importing it as failable. That is, an imported
precedence over importing it as fallible. That is, an imported
initializer with a nullable result and an error parameter would be
imported as throwing. Throwing initializers have very similar
constraints to failable initializers; in a way, it's just a new axis
of failability.
constraints to fallible initializers; in a way, it's just a new axis
of fallibility.

One limitation of this approach is that we need to be able to reconstruct
the selector to use when an overload of a method is introduced. For this
Expand Down