Cleanup the 'README.md' to remove stale content

artemcm · artemcm · commit 20cd6329b3ac · 2025-05-08T14:52:48.000-07:00
diff --git a/README.md b/README.md
@@ -1,8 +1,8 @@
 # Swift Compiler Driver
 
-Swift's compiler driver is a program that coordinates the compilation of Swift source code into various compiled results: executables, libraries, object files, Swift modules and interfaces, etc. It is the program one invokes from the command line to build Swift code (i.e., `swift` or `swiftc`) and is often invoked on the developer's behalf by a build system such as the [Swift Package Manager (SwiftPM)](https://github.com/swiftlang/swift-package-manager) or Xcode's build system.
+Swift's compiler driver is a program that coordinates the compilation of Swift source code into various compiled results: executables, libraries, object files, Swift modules and interfaces, etc. It is the program one invokes from the command line to build Swift code (i.e., `swift` or `swiftc`) and is often invoked on the developer's behalf by a build system such as the [Swift Package Manager](https://github.com/swiftlang/swift-package-manager) or [Swift Build](https://github.com/swiftlang/swift-build).
 
-The `swift-driver` project is a new implementation of the Swift compiler driver that is intended to replace the [existing driver](https://github.com/apple/swift/tree/main/lib/Driver) with a more extensible, maintainable, and robust code base. The specific goals of this project include:
+The `swift-driver` project is the primary implementation of the Swift compiler driver that has replaced the [legacy driver](https://github.com/apple/swift/tree/main/lib/Driver) with a more extensible, maintainable, and robust code base. Core pillars of the project's architecture include:
 
 * A maintainable, robust, and flexible Swift code base
 * Library-based architecture that allows better integration with build tools
@@ -11,8 +11,6 @@ The `swift-driver` project is a new implementation of the Swift compiler driver
 
 ## Getting Started
 
-**Note:** Currently, swift-driver is only compatible with trunk development snapshots from [swift.org](https://swift.org/download/#snapshots).
-
 The preferred way to build `swift-driver` is to use the Swift package manager.
 
 On most platforms you can build using:
@@ -27,27 +25,24 @@ However, on Windows, because Swift Package Manager does not differentiate betwee
 swift build -Xlinker "%SDKROOT%\usr\lib\swift\windows\x86_64\swiftCore.lib"
 ```
 
-To use `swift-driver` in place of the existing Swift driver, create a symbolic link from `swift` and `swiftc` to `swift-driver`:
+To use a locally-built `swift-driver` in place of the existing Swift driver, create a symbolic link from `swift` and `swiftc` to `swift-driver`:
 
 ```
 ln -s /path/to/built/swift-driver $SOME_PATH/swift
 ln -s /path/to/built/swift-driver $SOME_PATH/swiftc
 ```
 
-Swift packages can be built with the new Swift driver by overriding `SWIFT_EXEC` to refer to the `swiftc` symbolic link created above and `SWIFT_DRIVER_SWIFT_FRONTEND_EXEC` to refer to the original `swift-frontend`, e.g.,
+Swift packages can be built with the new Swift driver by overriding `SWIFT_EXEC` to refer to the `swiftc` symbolic link created above and `SWIFT_DRIVER_SWIFT_FRONTEND_EXEC` to refer to the original `swift-frontend`, e.g.
 
 ```
 SWIFT_EXEC=$SOME_PATH/swiftc SWIFT_DRIVER_SWIFT_FRONTEND_EXEC=$TOOLCHAIN_PATH/bin/swift-frontend swift build
 ```
 
-Similarly, one can use the new Swift driver within Xcode by adding a custom build setting (usually at the project level) named `SWIFT_EXEC` that refers to `$SOME_PATH/swiftc` and adding `-driver-use-frontend-path $TOOLCHAIN_DIR/usr/bin/swiftc` to `Other Swift Flags`.
+Similarly, one can use the Swift driver within Xcode by adding a custom build setting (usually at the project level) named `SWIFT_EXEC` that refers to `$SOME_PATH/swiftc`.
 
 ## Building with CMake
 
-`swift-driver` can also be built with CMake, which is suggested for
-environments where the Swift Package Manager is not yet
-available. Doing so requires several dependencies to be built first,
-all with CMake:
+`swift-driver` can also be built with CMake, which is suggested for environments where the Swift Package Manager is not yet available. Doing so requires several dependencies to be built first, all with CMake:
 
 * (Non-Apple platforms only) [swift-corelibs-foundation](https://github.com/apple/swift-corelibs-foundation)
 * [llbuild](https://github.com/apple/swift-llbuild) configure CMake with `-DLLBUILD_SUPPORT_BINDINGS="Swift"` and `-DCMAKE_OSX_ARCHITECTURES=x86_64` (If building on Intel) when building
@@ -64,7 +59,7 @@ cmake --build <swift-driver-build-dir>
 
 ## Developing `swift-driver`
 
-The new Swift driver is a work in progress, and there are numerous places for anyone with an interest to contribute! This section covers testing, miscellaneous development tips and tricks, and a rough development plan showing what work still needs to be done.
+Swift compiler driver is constantly evolving and improving, and there are numerous places for anyone with an interest to contribute! This section covers testing, and miscellaneous development tips and tricks.
 
 ### Driver Documentation
 
@@ -78,26 +73,6 @@ Test using command-line SwiftPM or Xcode.
 $ swift test --parallel
 ```
 
-Integration tests are costly to run and are disabled by default. Enable them
-using `SWIFT_DRIVER_ENABLE_INTEGRATION_TESTS` environment variable. In Xcode,
-you can set this variable in the scheme's test action.
-
-```
-$ SWIFT_DRIVER_ENABLE_INTEGRATION_TESTS=1 swift test --parallel
-```
-
-Some integration tests run the lit test suites in a Swift working copy.
-To enable these, clone Swift and its dependencies and build them with
-build-script, then set both `SWIFT_DRIVER_ENABLE_INTEGRATION_TESTS`
-and `SWIFT_DRIVER_LIT_DIR`, either in your Xcode scheme or
-on the command line:
-
-```
-$ SWIFT_DRIVER_ENABLE_INTEGRATION_TESTS=1 \
-  SWIFT_DRIVER_LIT_DIR=/path/to/build/Ninja-ReleaseAssert/swift-.../test-... \
-  swift test -c release --parallel
-```
-
 #### Testing against `swift` compiler trunk
 `swift-driver` Continuous Integration runs against the most recent Trunk Development snapshot published at [swift.org/download](https://swift.org/download/).
 
@@ -114,7 +89,7 @@ After the toolchain is installed, Xcode needs to be told to use it. This can mea
 
 Building with the toolchain is easy, set the toolchain in Xcode: Menu Bar > Xcode > Toolchains > select your toolchain
 
-Running the driver requires setting the TOOLCHAINS environment variable. This tells xcrun which toolchain to use (on darwin xcrun is used to find tools). This variable is the name of the toolchain and not the path (ex: `Swift Development Snapshot`). Important note: xcrun lookup is lower priority than the SWIFT_EXEC_*_EXEC family of environment variables, the tools directory, and any tools in the same directory as the driver (This includes a driver installed in a toolchain). Even though TOOLCHAINS is not highest priority it's a convenient way to run the xctest suite using a custom toolchain.
+Running the driver requires setting the TOOLCHAINS environment variable. This tells xcrun which toolchain to use (on darwin xcrun is used to find tools). This variable is the name of the toolchain and not the path (ex: `Swift Development Snapshot`). Important note: xcrun lookup is lower priority than the `SWIFT_EXEC_*_EXEC` family of environment variables, the tools directory, and any tools in the same directory as the driver (This includes a driver installed in a toolchain). Even though `TOOLCHAINS` is not highest priority it's a convenient way to run the xctest suite using a custom toolchain.
 
 #### Preparing a Linux docker for debug
 
@@ -155,51 +130,25 @@ $ .build/path/to/makeOptions > Sources/SwiftOptions/Options.swift
 
 ### Development Plan
 
-The goal of the new Swift driver is to provide a drop-in replacement for the existing driver, which means that there is a fixed initial feature set to implement before the existing Swift driver can be deprecated and removed. The development plan below covers that feature set, as well as describing a number of tasks that can improve the Swift driver---from code cleanups, to improving testing, implementing missing features, and integrating with existing systems.
+The development plan below covers a number of tasks that can improve the Swift driver---from code cleanups, to improving testing, implementing missing features, and integrating with existing systems.
 
 * Code and documentation quality
-  * [ ] Search for `FIXME:` or `TODO:`: there are lots of little things to improve!
-  * [ ] Improve documentation of how to incorporate the driver into your own builds
-  * [ ] Add useful descriptions to any `Error` thrown within the library
+  * Search for `FIXME:` or `TODO:`: there are lots of little things to improve!
+  * Improve documentation of how to incorporate the driver into your own builds
+  * Add useful descriptions to any `Error` thrown within the library
 * Option parsing
-  * [ ] Look for complete "coverage" of the options in `Options.swift`. Is every option there checked somewhere in the driver?
-  * [ ] Find a better way to describe aliases for options. Can they be of some other type `OptionAlias` so we can't make the mistake of (e.g.) asking for an alias option when we're translating options?
-  * [ ] Diagnose unused options on the command line
-  * [ ] Typo correction for misspelled option names
-  * [ ] Find a better way than `makeOptions.cpp` to translate the command-line options from [Swift's repository](https://github.com/apple/swift/tree/main/include/swift/Option) into `Options.swift`.
-* Platform support
-  * [x] Teach the `DarwinToolchain` to also handle iOS, tvOS, watchOS
-  * [x] Fill out the `GenericUnixToolchain` toolchain to get it working
-  * [x] Implement a `WindowsToolchain`
-  * [x] Implement proper tokenization for response files
-* Compilation modes
-  * [x] Batch mode
-  * [x] Whole-module-optimization mode
-  * [x] REPL mode
-  * [x] Immediate mode
-* Features
-  * [x] Precompiled bridging headers
-  * [x] Support embedding of bitcode
-  * [x] Incremental compilation
-  * [x] Parseable output, as used by SwiftPM
-  * [x] Response files
-  * [x] Input and primary input file lists
-  * [x] Complete `OutputFileMap` implementation to handle all file types uniformly
-* Testing
-  * [ ] Build stuff with SwiftPM or Xcode or your favorite build system, using `swift-driver`. Were the results identical? What changed?
-  * [x] Shim in `swift-driver` so it can run the Swift repository's [driver test suite](https://github.com/apple/swift/tree/main/test/Driver).
-  * [ ] Investigate differences in the test results for the Swift repository's driver test suite (above) between the existing and new driver.
-  * [ ] Port interesting tests from the Swift repository's [driver test suite](https://github.com/apple/swift/tree/main/test/Driver) over to XCTest
-  * [ ] Fuzz the command-line options to try to crash the Swift driver itself
-* Integration
-  * [x] Teach the Swift compiler's [`build-script`](https://github.com/apple/swift/blob/main/utils/build-script) to build `swift-driver`.
-  * [x] Building on the above, teach the Swift compiler's [`build-toolchain`](https://github.com/apple/swift/blob/main/utils/build-toolchain) to install `swift-driver` as the primary driver so we can test full toolchains with the new driver
+  * Look for complete "coverage" of the options in `Options.swift`. Is every option there checked somewhere in the driver?
+  * Find a better way to describe aliases for options. Can they be of some other type `OptionAlias` so we can't make the mistake of (e.g.) asking for an alias option when we're translating options?
+  * Diagnose unused options on the command line
+  * Typo correction for misspelled option names
+  * Find a better way than `makeOptions.cpp` to translate the command-line options from [Swift's repository](https://github.com/apple/swift/tree/main/include/swift/Option) into `Options.swift`.
 
 ### Build all Swift interfaces from an SDK
 Based on libSwiftDriver, `swift-build-sdk-interfaces`  is a tool to batch build all Swift textual interfaces (`.swiftinterface`) from an SDK into binary modules (`.swiftmodule`). As an example, the following command finds all Swift textual interface from the MacOSX SDK, builds all of them into binary modules, and outputs module-specific error logs into the given directory.
 
-`
-$SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk SWIFT_EXEC=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc swift-build-sdk-interfaces -o /tmp/outputs -v -log-path /tmp/logs`
+```
+$ $SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk SWIFT_EXEC=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc swift-build-sdk-interfaces -o /tmp/outputs -v -log-path /tmp/logs`
+```
 
 * *SDKROOT*: an env var to specify the SDK to work on
 * *SWIFT_EXEC*: teach `swift-build-sdk-interfaces` about where to find the Swift compiler to use
@@ -209,22 +158,10 @@ $SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/De
 
 ## Contributing to swift-driver
 
-Contributions to swift-driver are welcomed and encouraged! Please see the
-[Contributing to Swift guide](https://swift.org/contributing/).
-
-Before submitting the pull request, please make sure you have [tested your
- changes](https://github.com/apple/swift/blob/main/docs/ContinuousIntegration.md)
- and that they follow the Swift project [guidelines for contributing
- code](https://swift.org/contributing/#contributing-code).
+Contributions to swift-driver are welcomed and encouraged! Please see the [Contributing to Swift guide](https://swift.org/contributing/).
 
-To be a truly great community, [Swift.org](https://swift.org/) needs to welcome
-developers from all walks of life, with different backgrounds, and with a wide
-range of experience. A diverse and friendly community will have more great
-ideas, more unique perspectives, and produce more great code. We will work
-diligently to make the Swift community welcoming to everyone.
+Before submitting the pull request, please make sure you have [tested your changes](https://github.com/apple/swift/blob/main/docs/ContinuousIntegration.md) and that they follow the Swift project [guidelines for contributing code](https://swift.org/contributing/#contributing-code).
 
-To give clarity of what is expected of our members, Swift has adopted the
-code of conduct defined by the Contributor Covenant. This document is used
-across many open source communities, and we think it articulates our values
-well. For more, see the [Code of Conduct](https://swift.org/code-of-conduct/).
+To be a truly great community, [Swift.org](https://swift.org/) needs to welcome developers from all walks of life, with different backgrounds, and with a wide range of experience. A diverse and friendly community will have more great ideas, more unique perspectives, and produce more great code. We will work diligently to make the Swift community welcoming to everyone.
 
+To give clarity of what is expected of our members, Swift has adopted the code of conduct defined by the Contributor Covenant. This document is used across many open source communities, and we think it articulates our values well. For more, see the [Code of Conduct](https://swift.org/code-of-conduct/).
