Re: Seeing nil passed to isEqual:, despite non-null declaration
Re: Seeing nil passed to isEqual:, despite non-null declaration
- Subject: Re: Seeing nil passed to isEqual:, despite non-null declaration
- From: Sean McBride <email@hidden>
- Date: Fri, 13 Jan 2017 13:52:15 -0500
- Organization: Rogue Research Inc.
On Fri, 13 Jan 2017 10:43:09 -0800, Ben Kennedy said:
>> Did I miss a change in clang that made the default “not nullable”?? I
>read the above declaration as meaning that the nullability is
>*unspecified*, which implies that nil is allowed.
>
>NSObject.h (from which Sean was quoting) begins with
>NS_ASSUME_NONNULL_BEGIN which, to my understanding, makes everything in
>the file be non-nullable unless otherwise annotated.
I was going to say the exact same, but in fact usr/include/objc/NSObject.h does *not* contain NS_ASSUME_NONNULL_BEGIN, which I find quite surprising! Foundation's NSObject.h *does* however. What a mess.
Cheers,
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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