Brian Coyner • 2/10/2018

Using NS_REFINED_FOR_SWIFT

Read Original

This technical article details a solution for bridging Objective-C methods that return NSInteger (like NSNotFound for errors) to Swift more elegantly. It demonstrates using the NS_REFINED_FOR_SWIFT macro to hide the original API and provide a Swifty wrapper that throws errors, improving code clarity and safety in mixed-language projects.

0 comments
#Swift #Interoperability #Objective C
Using NS_REFINED_FOR_SWIFT

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
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes