mirror of
https://github.com/apple/swift.git
synced 2026-01-17 12:17:35 +01:00
25e1c9f52a
These two modules themselves depend on modules that implicitly import the _StringProcessing library. Take OSLog as an example, which imports ObjectiveC, which implicitly imports _StringProcessing. Thus, we can get into the following bad scenario: - A compiler at module format X builds _StringProcessing - A rebase is performed and the compiler is rebuilt at module format Y > X - OSLog builds before _StringProcessing (since it has no dependency) - But _StringProcessing is at module format X < Y, so we have to rebuild it This normally manifests as an error at the desks of compiler engineers about a mismatch in the module format for _StringProcessing. Let's fix that by making CMake schedule _StringProcessing before them.
The modules in the 'stdlib/private' directory contain APIs that are considered private to the Swift project. Don't use them outside of the repositories related to the Swift project. These APIs are used for building Swift build and test automation tools, represent early prototypes of APIs that are not intended to be included in the standard library soon, modules to support ports to other platforms, and other similar needs that are private to the Swift project and its development process.