> On Oct 13, 2015, at 10:13 PM, Charles Srstka <cocoa...@charlessoft.com> wrote:
>
>> On Oct 13, 2015, at 10:27 PM, Shane Stanley <sstan...@myriad-com.com.au>
>> wrote:
>>
>> On 14 Oct 2015, at 1:33 PM, Graham Cox <graham....@bigpond.com> wrote:
>>>
>>> I’ve been passing nil forever, only now does Xcode 7 complain, presumably
>>> because only now is the _Nonnull attribute added. But either the
>>> documentation or the addition of _Nonnull is wrong.
>>
>> FWIW, I've had an open bug on this since July (#21667200). You might also
>> notice the docs say "dict can be nil", and there isn't a "dict" to be seen
>> (presumably it means docAttributes).
>
> I actually reported this one back in June (rdar://21314130). Mine got closed
> with this as the rationale:
>
> "This issue behaves as intended based on the following:
>
> It’s intended to log warnings.
>
> We are now closing this bug report.”
>
> Hopefully that makes sense to someone. (In fairness, it does seem that the
> Radar was re-opened sometime in the meantime, though, as it’s showing up as
> “Open” now. Not sure if that's due to the protestations I added to the
> report, or due to the radar you filed in July.)
The intended meaning was “the warning (about passing nil) is intended”. The
helpful followup is that it is generally encouraged to use empty containers
(@[] or @{}) over nil when there is no semantic difference, as is the case for
the aforementioned API.
--
David Duncan
_______________________________________________
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
