I believe this has already been fixed here: <a href="https://github.com/apple/swift/commit/f524802e129f17de16fa6f8c3f08e5bcf75cc581">https://github.com/apple/swift/commit/f524802e129f17de16fa6f8c3f08e5bcf75cc581</a><br><div class="gmail_quote"><div dir="ltr">On Thu, Dec 17, 2015 at 10:01 Félix Cloutier <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Initializers can now fail, but objects still need to be fully initialized before you can return `nil` from them. For instance:<br>
<br>
class Foo {<br>
let bar: Int<br>
init?(baz: Int) {<br>
guard baz < 100 else {<br>
return nil<br>
}<br>
self.bar = baz<br>
}<br>
}<br>
<br>
This trivial example causes the following error: "all stored properties of a class instance must be initialized before returning nil from an initializer".<br>
<br>
For integers, that's easy: you can simply set them to zero. However, sometimes, you'd want initialization to fail because the arguments you received don't allow you to properly initialize a member. In these cases, you have to make the fields Optionals (implicitly unwrapped or not) to overcome this.<br>
<br>
I remember that Chris said that this is a temporary issue and that it would eventually be fixed. I'm starting this thread because I'd love to have this with or before Swift 3 and I'd like to see who thinks this is big enough of an issue to rival the proposals we already have.<br>
<br>
Félix<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>