Jordan
Congrats to my Swift colleagues for #finally pushing @c over the finish line! Been a long time coming.
Mar 26 at 8:29pmWeb
Show threadJordan1d ago
Context: Swift has not officially had a way to expose plain old functions to C until now. Why? Because it had Objective-C interoperability first, and so deciding whether C functions should support everything ObjC does or not was…complicated. You can read about it here: https://github.com/swiftlang/swift-evolution/blob/main/proposals/0495-cdecl.md
Show threadpenryu1d ago
@jrose Thank you for calling this out. A lot of people don't realize just how much of Swift's design was influenced by the need for ObjC interop.
Show threadJordan1d ago
@penryu so, so much
Show threadCurt1d ago
@jrose oh gosh, yes please. I once had to wrap my Swift code in Obj-C then that was to be called from C. Not fun.
Show threadHelge Heß1d ago
@jrose But but, it’s Objective-C w/o the C?! Have we’ve been lied to all the time?
Show threadJordan1d ago
@helge “Swift 6.3: Objective-C, without the C, with the C.”
Show threadHelge Heß1d ago
@jrose Objective-C, without the C, with the C, C++ actually, w/o the Objective
Show threadJoe Groff (1M Context)1d ago
@jrose @helge the Swift of Theseus
Show thread✾, chief troublemaker1d ago
@jrose YESSSSSSSSSS I missed that!
Show threadBecca Royal-Gordon1d ago
@jrose I also got module selectors in, so it’s a good release for #finally fans.
Show threadBecca Royal-Gordon1d ago
@jrose (It’s not used in module interfaces by default yet, but we have that in main.)
Show threadJordan1d ago
@beccadax Yeah, you (pl and sg) do deserve kudos for this too! I just remembered you already posting about it, whereas nobody had been posting about @c (maybe because Alexis has better things to do with his time than we do)