5 Commits

Author	SHA1	Message	Date
Owen Voorhees	f04b971726	Adopt swift-tools-protocols	2025-10-31 14:11:11 -07:00
Ben Barham	add109d2d8	Avoid crashing when loading client plugins from the same path ... When `DYLD_(FRAMEWORK|LIBRARY)_PATH` is set, `dlopen` will first check if the basename of the provided path is within any of its search paths. Thus it's possible that only a single library is loaded for each toolchain, rather than a separate like we expect. The paths should be equal in this case, since the client plugin is loaded based on the path of `sourcekitd.framework` (and we should only have one for the same reason). Allow this case and just avoid re-initializing.	2025-09-26 12:22:59 -07:00
Alex Hoppen	92aa94fa43	Remove the split between SourceKitD and DynamicallyLoadedSourceKitD ... There is only one real class that implements the `SourceKitD` protocol, so there really isn’t any need for the protocol + class split at all. Unify them to make code simpler to reason about.	2025-03-27 11:05:24 -07:00
Alex Hoppen	1cfa8db1d8	Require Swift 6 to build SourceKit-LSP ... This significantly cleans up our `import` statements	2025-03-07 08:05:49 -08:00
Alex Hoppen	1c3e5bb724	Communicate the path of sourcekitd that the plugin was loaded from to the plugin	2025-01-09 14:09:01 +01:00