You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SR-104 Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes
Issue Description:
Would it be possible to get either an option to change the compiler behavior to choose different nullability behavior or give a companion to `NS_ASSUME_NONNULL_BEGIN` with the opposite effect?
As is, applying `null_unspecified` to everything coming out of ObjC seems to encourage unsafe assumptions about what you're getting out of an ObjC function.
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: 807459f0cb45811e0f8f067d612e0a07
relates to:
Issue Description:
Would it be possible to get either an option to change the compiler behavior to choose different nullability behavior or give a companion to `NS_ASSUME_NONNULL_BEGIN` with the opposite effect?
As is, applying `null_unspecified` to everything coming out of ObjC seems to encourage unsafe assumptions about what you're getting out of an ObjC function.
The text was updated successfully, but these errors were encountered: