Re: Swift 2 throws from init()
Re: Swift 2 throws from init()
- Subject: Re: Swift 2 throws from init()
- From: Rick Mann <email@hidden>
- Date: Wed, 01 Jul 2015 17:50:45 -0700
> On Jul 1, 2015, at 17:48 , Quincey Morris <email@hidden> wrote:
>
> On Jul 1, 2015, at 17:39 , Rick Mann <email@hidden> wrote:
>>
>> What's the run-time penalty of using implicitly- or force-unwrapped Optionals? Does it do a check for null at each invocation, or does it crash?
>
> I’d propose that not returning from the initializer at all is a better solution. If there’s no reasonable *recovery* from this situation, why is it helpful simply to push the problem upstream?
I didn't think it was possible to not return. Maybe an assert() is better in this situation, because I think it always indicates a programming mistake. At least so far, I've never used my (originally C++) Core Graphics wrapper in any situation in which a lack of context was something I could handle.
--
Rick Mann
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden