Skip to content

Migration tooling for Swift features #2673

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.

Sign up for GitHub

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 21 commits into from
May 21, 2025
Merged

Migration tooling for Swift features #2673

Changes from 1 commit
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
7d2ae4e
burp
AnthonyLatsis Jan 29, 2025
dafb468
burp
AnthonyLatsis Feb 14, 2025
a7ea7ae
burp
AnthonyLatsis Feb 14, 2025
80fa278
burp
AnthonyLatsis Feb 14, 2025
8707bf7
Editorial pass over the introduction section.
hborla Feb 15, 2025
593a069
Editorial pass over the automation section.
hborla Feb 15, 2025
78fd5a2
Clarify that future proposals introducing upcoming features should in…
hborla Feb 15, 2025
9bedf55
burp 0.9
AnthonyLatsis Feb 17, 2025
2c60494
burp 0.10
AnthonyLatsis Feb 17, 2025
1830066
Use `DisableOutwardActorInference` in the example for the "User inten…
hborla Feb 17, 2025
7d62c54
Move source incompatible changes to Future directions.
hborla Feb 17, 2025
036815c
burp 1.0
AnthonyLatsis Feb 17, 2025
24e26bb
Add link to pitch
AnthonyLatsis Feb 19, 2025
c6039af
Minor clarification for naming rationale
AnthonyLatsis Feb 19, 2025
31ff678
Describe the behavior for specifying invalid mode
AnthonyLatsis Feb 19, 2025
8ae57e8
Clarify diagnostic group for a proposed warning
AnthonyLatsis Feb 20, 2025
60a1491
"adopt" -> "migrate" & alternatives considered
AnthonyLatsis Mar 17, 2025
a88c177
Minor wording amendment
AnthonyLatsis Mar 18, 2025
a87b818
Move `swift migrate` from Future Directions to Detailed Design section
xedin Apr 30, 2025
84c2fca
Add Alternatives Considered section for `swift migrate` vs. `swift pa…
xedin May 16, 2025
e4b2583
Replace `swift migrate` with `swift package migrate`
xedin May 19, 2025
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
Prev Previous commit
Next Next commit
Clarify diagnostic group for a proposed warning
  • Loading branch information
@AnthonyLatsis
AnthonyLatsis committed Feb 20, 2025
commit 8ae57e809cfbe17a549fff127b006bf54cbecfdd
5 changes: 3 additions & 2 deletions proposals/NNNN-adoption-tooling-for-swift-features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,7 @@ for a given upcoming feature, i.e., because the upcoming feature does not
have a mechanical migration.
A corresponding warning will be emitted in this case to avoid the false
impression that the impacted source code is compatible with the feature.
This warning will belong to the diagnostic group `StrictLanguageFeatures`.

### Interface

Expand All @@ -149,8 +150,8 @@ For example:
```

If the specified mode is invalid, the flag will be ignored, and a warning will
be emitted. This warning will belong to the `StrictLanguageFeatures` diagnostic
group.
be emitted.
This warning will belong to the diagnostic group `StrictLanguageFeatures`.
In a series of either of these options applied to a given feature, only the
last option will be honored.
If an upcoming feature is both implied by the effective language mode and
Expand Down