Alex Hoppen
Alex Hoppen
Depends on https://github.com/swiftlang/sourcekit-lsp/pull/2093 --- Just something I noticed while looking through code. I am not aware of any issues caused by this. Also relax the `precondition` in `DLHandle.deinit` to a...
Depends on https://github.com/swiftlang/sourcekit-lsp/pull/2093. --- This way we can log them when a sourcekitd request crashes and we can thus replay these contextual requests when diagnosing the crash.
When we send a `SIGKILL` to a subprocess, it only terminates that process and not its child processes. Similarly, on Windows, calling `TerminateProcess` only terminates that process and not its...
We never ran the macro expansion tests on Windows because the tricks we do in `macroPackageManifest` to avoid rebuilding swift-syntax during test execution don’t work on Windows Swift CI, where...
When we have build settings for a file, we should be able to use those when parsing the SwiftSyntax tree. Currently, we always create the SwiftSyntax tree with all experimental...
We should be able to raise the deployment target of SourceKit-LSP to macOS 14.0 and thus use the atomics from the standard library.
When switching to a different toolchain, the index-build folder isn’t really in a valid state anymore (eg. all the preparation state is out-of-date). We should re-index the project when we...
The index build and the real build maintain two separate checkouts of the package dependencies. Because of this, jump-to-definition takes you to the source file in the `.build/index-build` folder, while...
We currently rebuild swift-syntax, swift-foundation-icu and swift-foundation twice: Once to test swift-foundation and once to test swift-corelibs-foundation. Using a unified build for both projects means that we only need to...
If I have ```swift public protocol Foo { @_spi(A) func foo() } extension Foo { @_spi(A) public func foo() {} } ``` and a second module with ```swift import Lib...