Swift-AI VS sourcekit-lsp

Before CoreML was released (and also before BNNS), I wrote SwiftAI. The project made heavy use of Accelerate and the algorithms were written from scratch. It was a great project, and I planned to make a lot of additions, but CoreML came out pretty soon afterward and made the project mostly obsolete. Still a great learning experience and there was a fair bit of interest at the time.

Great！By the way，you can also use sourcekit-lsp and xcode-build-server to program in neovim directly。though still need to debug in xcode。

After enabling eglot, our local files will not be picked up by language server. Because the documentation(https://github.com/apple/sourcekit-lsp) mentions "IndexStoreDB is built using the Swift Package Manager."

Created an issue: https://github.com/apple/sourcekit-lsp/issues/636

For Objective C it looks like you can use SourceKit-LSP or ccls as language servers.

git clone https://github.com/apple/sourcekit-lsp.git cd sourcekit-lsp/Editors/vscode/ npm install npm run dev-package code --install-extension sourcekit-lsp-development.vsix

There's already an LSP server for Swift (also made for Apple): https://github.com/apple/sourcekit-lsp

This library is intended for syntactic tools: formatters, highlighters, that kind of thing.

You could probably set up something to work on Swift packages, however the tree sitter grammar for Swift hasn’t been updated since 2019. sourcekit-lsp also isn’t likely to help you out either because it’s not made to understand Xcode projects. You’d need an LSP capable of parsing a .pbxproj (I highly doubt there is one, but I haven’t looked around), which has the terrible downside of not being something Apple considers a public API and can and will introduce breaking changes on any Xcode update. An Apple engineer confirmed this with me during a lab in 2020 when I was asking about how doing some hacky things with binary Swift packages.