Re:Swift for C++ Practitioners, Part 1: Intro and Value Types
by Zanfa on Monday April 15, 2024 @06:22AM
(#40038632)
What works quite well for iOS/macOS apps is breaking the project into a barebones Xcode project plus a Swift package that contains all of the code. SPM projects work well with VSCode and you get full auto-complete support with the official Swift plugin.
Re:Swift for C++ Practitioners, Part 1: Intro and Value Types
by terhechte on Monday April 15, 2024 @07:24AM
(#40039071)
Thanks for the suggestion, I'll give that a try. Obviously this will not work with large existing codebases; but for new projects I'll try how well it works.
Re:Swift for C++ Practitioners, Part 1: Intro and Value Types
by userm0d on Monday April 15, 2024 @10:07AM
(#40040729)
We already have a NeoVim plugin [0] that makes replacing Xcode somewhat possible. It's not perfect and requires that you have Xcode around for certain scenarios but I have been using it as my daily driver for the last month.
I think you would only need xcode-build-server [1] in order to get autocompletion in VSCode.
The advantage for Swift would be that potentially more developers use the VSCode extension which would hopefully improve the quality and incentivise more of them to maybe contribute to it.
If it's already possible then maybe a section in the readme on how to achieve this? (e.g. how to open an iOS project folder and get completions for Apple's frameworks).