Assumptions != NSNotFound
Read OriginalThe article details a specific Objective-C programming pitfall where calling `rangeOfString:` on a nil NSString returns a struct with zeros, not NSNotFound. This causes logic errors, as the check `range.location != NSNotFound` incorrectly passes. It contrasts this with Swift's safer optionals and recommends using `containsString:` on iOS 8+.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
The Beautiful Web
Jens Oliver Meiert
•
2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane
•
1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg
•
1 votes
4
Wagon’s algorithm in Python
John D. Cook
•
1 votes
5
An example conversation with Claude Code
Dumm Zeuch
•
1 votes