objective c - Should I use nullable/nonnull in implementation file -


i want use objective-c nullability feature. should annotate nullable/nonnull implementation file or interface?

the reason declare nullability have warning feedbacks compiler unit (see https://developer.apple.com/swift/blog/?id=25 ).

as best practice, should set nullable , nonnull (or _nullable , _nonnull) in declarations.

so should interfaces, depending on coding standards, may implement class-scoped (or category-scoped) methods without declaring them, , in case declaration implementation , should declare nullability values.

you can declare nullability implementations declared in interfaces, in opinion degrades maintainability.


Comments

Popular posts from this blog

OpenCV OpenCL: Convert Mat to Bitmap in JNI Layer for Android -

android - org.xmlpull.v1.XmlPullParserException: expected: START_TAG {http://schemas.xmlsoap.org/soap/envelope/}Envelope -

python - How to remove the Xframe Options header in django? -