NS_ASSUME_NONNULL_BEGIN && NS_ASSUME_NONNULL_END
2016-09-29 15:40
417 查看
__nullable指代对象可以为NULL或者为NIL
__nonnull指代对象不能为null
参考博客 : http://www.jianshu.com/p/b3a31eed945f
__nonnull指代对象不能为null
参考博客 : http://www.jianshu.com/p/b3a31eed945f
相关文章推荐
- NS_ASSUME_NONNULL_BEGIN和NS_ASSUME_NONNULL_END
- NS_ASSUME_NONNULL_BEGIN,NS_ASSUME_NONNULL_END
- NS_ASSUME_NONNULL_BEGIN和NS_ASSUME_NONNULL_END详解
- NS_ASSUME_NONNULL_BEGIN和NS_ASSUME_NONNULL_END是做什么的?
- NS_ASSUME_NONNULL_BEGIN,NS_ASSUME_NONNULL_END
- NS_ASSUME_NONNULL_BEGIN和NS_ASSUME_NONNULL_END详解
- iOS NS_ASSUME_NONNULL_BEGIN __nullable __nonnull 使用
- NS_ASSUME_NONNULL_BEGIN 延伸
- Unbalanced calls to begin/end appearance transitions for <BindDoctorSuccessViewController: 0x1682db4
- Ruby 入门: BEGIN & END
- STL中的back()&&end()||front()&&begin()辨析
- Unbalanced calls to begin/end appearance transitions for <UIViewController>
- Unbalanced calls to begin/end appearance transitions for <uivewcontroller>
- Unbalanced calls to begin/end appearance transitions for <UINavigationController: 0xac500c0>.
- __proc_info_begin->__proc_info_end
- c# begin & end.
- delegate BeginInvoke& EndInvoke
- begin&amp;end
- Why “transform(s.begin(),s.end(),s.begin(),tolower)” can't be complied successfully?
- Unbalanced calls to begin/end appearance transitions for <> 自定义tabbar问题