Saleem Abdulrasool
Saleem Abdulrasool
Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate. Resolves #NNNNN, fix apple/llvm-project#MMMMM.
When building LSP with SPM we hit the export symbol limits: ``` lld-link: error: too many exported symbols (max 65535) clang: error: linker command failed with exit code 1 (use...
tools-support-core has dropped this dependency which now allows us to remove the dependency as well.
Windows switched a while ago to statically linking the full SourceKit-LSP binary because it netted a size win (reduction). The recent dependency on SwiftSyntax may change the calculus, particularly with...
Simply adjust the variable name spelling rather than duplicate the logic. This is a minor cleanup, NFC. Co-authored-by: Alex Hoppen
Pull down a number of upstream changes for the build system. Additionally add some inflight changes. This overhaul simplifies the configuration and uses standard build options now e.g. `BUILD_SHARED_LIBS`, `BUILD_TESTING`...
The current implementation just iterates over the changed files, which results in problems when files are removed. Example run: https://github.com/compnerd/swift-win32/pull/548/checks?check_run_id=2616414119
It seems that the command execution does not handle paths with spaces. An example run at https://github.com/compnerd/swift-win32/pull/537/checks?check_run_id=2594778733 demonstrates the issue. `swift-format` will treat the unquoted path as two separate paths...
It seems that this action doesn't report the lint issues when run on Windows. I don't see instructions on getting started for the action so it is a bit difficult...
Repair the error reporting on Windows in the case of a failure in `SHGetKnownFolder` - the returned value is a `HRESULT`, which is the extended error code unlike the Win32...