Don't emit @noescape error on every "@autoclosure is now a ..." error #4017
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the @NoEscape is implicitly added by the @autoclosure this diagnostic is superfluous. It's also actively harmful for migration, since it still inserts a fixit to insert the @NoEscape. rdar://problem/27667515
|
@swift-ci Please test |
|
@nkcsgexi could you please review? |
|
LGTM! |
kateinoigakukun
pushed a commit
that referenced
this pull request
Aug 31, 2022
[pull] swiftwasm from main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's in this pull request?
@autoclosureused on a parameter (instead of its type) we were also diagnosing the implicit@noescapeattribute. This diagnostic showed up at<unknown>:0:, but still inserted a fixit to add the noescape attribute to the parameter type, resulting in invalid code.@autoclosureparameters.Resolved bug number: (SR-)
rdar://problem/27667515
Before merging this pull request to apple/swift repository:
Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
A smoke test on macOS does the following:
device standard libraries are not built.
version of these tests are not run.
A smoke test on Linux does the following:
tests are not run.
Validation Testing
Lint Testing
Note: Only members of the Apple organization can trigger swift-ci.
If the @NoEscape is implicitly added by the @autoclosure this
diagnostic is superfluous. It's also actively harmful for migration,
since it still inserts a fixit to insert the @NoEscape.
rdar://problem/27667515