Skip to content

Clarify unsupported direct macro module imports in CHANGELOG.md #7754

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

Merged
merged 1 commit into from
Jul 8, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,9 @@ Swift 6.0
`--experimental-swift-sdks-path` options on `swift build` are deprecated with replacements that don't have the
`experimental` prefix.

* [#7535] The `swift sdk configuration` subcommand is deprecated with a replacement named `configure` that has options that exactly match
* [#7535]

The `swift sdk configuration` subcommand is deprecated with a replacement named `configure` that has options that exactly match
[SE-0387 proposal text].

* [#7202]
Expand All @@ -34,6 +36,9 @@ Swift 6.0

Macros cross-compiled by SwiftPM with Swift SDKs are now correctly built, loaded, and evaluated for the host triple.

Packages with modules that incorrectly imported macro modules directly instead of importing macro interface modules will no longer build
with `swift build`.

Swift 5.10
-----------

Expand Down