swift VS sourcekit-lsp

Because of C/C++ interop, and integration with CMake, you can just add Swift to a Zephyr project and it pretty much Just Works. [The docs](https://github.com/apple/swift/blob/main/docs/EmbeddedSwift/...) should mostly apply to the Zephyr SDK as well.

Fortunately, the Observation framework is part of the Swift 5.9 standard library. We can learn more information by examining its source code.

They do! See https://github.com/apple/swift/blob/main/docs/LibraryEvoluti...

You can also see an example of what a different high level language integration with Swift ABI looks like here: https://github.com/dotnet/designs/blob/main/proposed/swift-i...

So is differentiable Swift a package for Swift or is it part of the Swift standard library? The video says go to swift.org but I can't find any info about differentiable Swift on that site.

Swift's Differentiable Programming Manifesto. Swift has a powerful differentiable programming component, integrated with the compiler.

You can do the same thing the other way around - https://github.com/apple/swift/blob/main/docs/Android.md.

Codable (along with other derived conformances like Equatable, Hashable, and RawRepresentable) is indeed built in to the compiler[0], but unlike Serde, it operates during type-checking on a fully-constructed AST (with access to type information), manipulating the AST to insert code. Because it operates at a later stage of compilation and at a much higher level (with access to type information), the work necessary is significantly less.

With ongoing work for Swift macros, it may eventually be possible to rip this code out of the compiler and rewrite it as a macro, though it would need to be a semantic macro[1] rather a syntactic one, which isn't currently possible in Swift[2].

[0] https://github.com/apple/swift/blob/main/lib/Sema/DerivedCon...

`Int` is a regular struct with a single stored property of type `Builtin.Word` . But the latter is a magical compiler built-in. Source for integer types is generated from this template - https://github.com/apple/swift/blob/9da65ca0a15fdf341649c994b0a77ec3b71f2687/stdlib/public/core/IntegerTypes.swift.gyb

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.