-
Notifications
You must be signed in to change notification settings - Fork 1.4k
SwiftFixIt: Misc improvements #8671
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
Conversation
This will make it harder to make note vs. primary diagnostic mistakes in tests.
`joined()` already returns a lazy collection.
These diagnostics generally require user intervention.
case 0: | ||
// No notes have fix-its. Skip if neither does the primary | ||
// diagnostic. | ||
guard diagnostic.hasFixIt else { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, I wonder if we have cases where both a diagnostic and its notes have fix-its? If seems like if the diagnostic has fix-its we should use them since that should be considered a "default" behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let’s find out. At first thought that sounds like something we’d want to discourage in favor of a note.
@swift-ci please test |
The minimum Swift tools version is appropriate for noncopyable types.
0e8eddb
to
3083a80
Compare
@swift-ci please test |
@swift-ci please test Windows platform |
### Modifications: * Test reorg. * More tests. * When we skip primary diagnostics, skip their notes too. * Skip primary diagnostics with more than 1 note with fix-its. * Deduplicate primary diagnostics. (cherry picked from commit 64b4746)
Modifications: