From 1acefadcf7f9a87cc3b384b8075145c01f39899c Mon Sep 17 00:00:00 2001 From: Young Seok Tony Kim Date: Fri, 4 Dec 2015 23:20:53 +0900 Subject: [PATCH] Fixed typo : failable -> fallible --- docs/ErrorHandling.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/ErrorHandling.rst b/docs/ErrorHandling.rst index 0b2424a25d571..12602fa0f0b6e 100644 --- a/docs/ErrorHandling.rst +++ b/docs/ErrorHandling.rst @@ -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