-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove support for legacy .swift-testing binary #994
Labels
macOS
Issues specific to macOS
Comments
plemarquand
added
enhancement
New feature or request
macOS
Issues specific to macOS
and removed
enhancement
New feature or request
labels
Aug 7, 2024
plemarquand
added a commit
to plemarquand/vscode-swift
that referenced
this issue
Sep 3, 2024
The .swift-testing binary is no longer output, it has been rolled in to a single binary for both XCTest and Swift Testing we no longer need to test for this distinction now that the nightly toolchains have been producing this unified binary for enough time. Issue: swiftlang#994
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once Swift 6.0 and Xcode 15 have been finalized and released, refactor the build config generation code to assume a unified test binary.
#986 introduced support for a unified binary but retained support for running the old
.swift-testing
binary if the user had a 6.0 toolchain that still generated it. Once we're confident users have moved on to generating a unified binary the build config generation can be simplified and the code path for the legacy swift-testing binary can be removed.More context in the comment here:
https://github.com/swiftlang/vscode-swift/pull/986/files#diff-ed1fc3b638d3e40c8a0266ffea55087d5c16ef1bede54e612f8c1b3f6534288bR449
The text was updated successfully, but these errors were encountered: