[Concurrency/Diagnostics] A few fixes to diagnostic downgrades and tracking #79599
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Avoid downgrading diagnostics multiple times
Unify
warn
+limitBehavior
into a single call to make surethat diagnostic doesn't get downgraded multiple times because
that could affect how diagnostics are tracked.
Don't account ignored diagnostics in
Sema.NumSwift6Errors
statisticSince the diagnostic is not going to be emitted counting it in
Swift6Errors
statistics is going to be confusing to the users.Resolves: #79291
Resolves: rdar://145341605