Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[SR-223] Option to assume ObjC return values are always nullable #42845

Open
swift-ci opened this issue Dec 14, 2015 · 0 comments
Open

[SR-223] Option to assume ObjC return values are always nullable #42845

swift-ci opened this issue Dec 14, 2015 · 0 comments
Labels
improvement

Comments

@swift-ci
Copy link
Collaborator

Previous ID SR-223
Radar None
Original Reporter ultramiraculous (JIRA User)
Type Improvement
Additional Detail from JIRA
Votes 1
Component/s
Labels Improvement
Assignee None
Priority Medium

md5: 807459f0cb45811e0f8f067d612e0a07

relates to:

  • 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.
@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@swift-ci