Skip to content

[Concurrency/Diagnostics] A few fixes to diagnostic downgrades and tracking #79599

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 2 commits into from
Feb 25, 2025

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Feb 25, 2025

  • Avoid downgrading diagnostics multiple times

    Unify warn + limitBehavior into a single call to make sure
    that diagnostic doesn't get downgraded multiple times because
    that could affect how diagnostics are tracked.

  • Don't account ignored diagnostics in Sema.NumSwift6Errors statistic

    Since 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

Unify `warn` + `limitBehavior` into a single call to make sure
that diagnostic doesn't get downgraded multiple times because
that could affect how diagnostics are tracked.
…t6Errors` statistic

Since the diagnostic is not going to be emitted counting it in
`Swift6Errors` statistics is going to be confusing to the users.

Resolves: swiftlang#79291
Resolves: rdar://145341605
@xedin
Copy link
Contributor Author

xedin commented Feb 25, 2025

@swift-ci please test

@xedin xedin merged commit fabe70e into swiftlang:main Feb 25, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

False positives reported in Sema.NumSwift6Errors via -stats-output-dir
2 participants