> On Jul 1, 2015, at 17:48 , Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > On Jul 1, 2015, at 17:39 , Rick Mann <rm...@latencyzero.com> 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 rm...@latencyzero.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
