Xcode 14.3 Analyzer Warnings Related To Assumed Nullability #391
Comments
LowAmmo
added a commit
to LowAmmo/libPhoneNumber-iOS
that referenced
this issue
May 12, 2023
…unctions * Address analyzer warnings related to passing nil to non-nil parameters
LowAmmo
added a commit
to LowAmmo/libPhoneNumber-iOS
that referenced
this issue
May 12, 2023
…unctions * Address analyzer warnings related to passing nil to non-nil parameters * Fix build failure with 'ShortNumber' test target
|
Created Pull Request: #392
Everything was tested/developed with Xcode 14.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running Xcode analyzer on our project (and directly on the libPhoneNumber-iOS project), seeing some warnings about passing nil to methods that are expecting it, or returning nil from methods that don't support returning nil.
Working under an assumption that the current code is doing what is desired, I believe the majority of the "issues" are just due to assumed Nullability with methods.
I'm working on a PR that adds nullability specifiers primarily in NBPhoneNumberUtil, but also a few other places that gave warnings.
Everything seems to be benign, so not sure there is actually a problem - but, my OCD appreciates when code analysis doesn't produce any warnings at all. 😄
The text was updated successfully, but these errors were encountered: