Improving the usability of C libraries in Swift

Re:Improving the usability of C libraries in Swift by andeee23 on Friday January 23, 2026 @02:18AM (#46729493)

i’m not sure about the work on tooling

just a few weeks ago i was trying to work on a swift project in neovim and found the whole langserver experience pretty bad

and it’s way worse when working on swif ui apps, but i guess that’s more of an apple wanting you to use xcode thing.

i wish there was better tooling, i like the language, but i just switched to nim for my side project

[ Parent | on HN ]

Re:Improving the usability of C libraries in Swift by pentamassiv on Friday January 23, 2026 @02:52AM (#46729721)

I find the Swift tooling very lacking. There's no way to lint dead code, there no way to auto format the files exactly as Xcode would do it and tell the linter those rules so that it doesn't lint your auto formatted code. Xcode project files are impossible to edit except with Xcode and Xcode often has issues and I need to manually empty the build folder. These are just some of the issues I remember

[ Parent | on HN ]

Re:Improving the usability of C libraries in Swift by pharaohgeek on Friday January 23, 2026 @09:21AM (#46732796)

I do miss JetBrains' AppCode and their support for Swift in CLion. I wish they would open-source those plugins so that they can continue to be used in modern versions of CLion.

[ Parent | on HN ]