> On Feb 10, 2016, at 6:21 AM, Dave <d...@looktowindward.com> wrote: > > I’m subclassing and overriding methods on a Class that has nullable/non null > syntax enabled. I getting a warning on the following declaration: > > -(nullable LTWNodeInfo*) getNodeAtIndexPath:(nonnull NSIndexPath*) > theIndexPath error:(NSError**) theErrorPtr;
That’s weird, because I’ve added nullability declarations on my public APIs, and I haven’t had to add any annotations on NSError** parameters. I am putting NS_ASSUME_NONNULL_BEGIN above the declarations in each header and NS_ASSUME_NONNULL_END at the end. These macros expand to Clang pragmas. Maybe while in that mode the compiler knows that NSError** parameters are nullable? Are you using those macros? —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
