Skip to content

[Parse] Attach 'inout' to Swift 2 unparenthesized function params. #4248

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

Conversation

jrose-apple
Copy link
Contributor

  • Explanation: Swift 2 parsed inout parameters with function types slightly differently than Swift 3 does, which leads to non-semantics-preserving fix-its when using Swift-2-style unparenthesized functions.
  • Scope: Only affects inout parameters, and then should only affect those using Swift-2-style functions.
  • Issue: rdar://problem/26681485
  • Reviewed by: @nkcsgexi
  • Risk: Low.
  • Testing: Added new compiler regression tests.

Before merging this pull request to apple/swift repository:

  • Test pull request on Swift continuous integration.

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

Platform Comment
All supported platforms @swift-ci Please smoke test
All supported platforms @swift-ci Please smoke test and merge
OS X platform @swift-ci Please smoke test OS X platform
Linux platform @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

  1. Builds the compiler incrementally.
  2. Builds the standard library only for macOS. Simulator standard libraries and
    device standard libraries are not built.
  3. lldb is not built.
  4. The test and validation-test targets are run only for macOS. The optimized
    version of these tests are not run.

A smoke test on Linux does the following:

  1. Builds the compiler incrementally.
  2. Builds the standard library incrementally.
  3. lldb is built incrementally.
  4. The swift test and validation-test targets are run. The optimized version of these
    tests are not run.
  5. lldb is tested.

Validation Testing

Platform Comment
All supported platforms @swift-ci Please test
All supported platforms @swift-ci Please test and merge
OS X platform @swift-ci Please test OS X platform
OS X platform @swift-ci Please benchmark
Linux platform @swift-ci Please test Linux platform

Lint Testing

Language Comment
Python @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

…wiftlang#4241)

This syntax is no longer permitted, but we need to parse it like Swift
2 did in order to produce the fix-it that matches Swift 2 behavior.

rdar://problem/26681485
(cherry picked from commit 294bbd8)
@jrose-apple jrose-apple added this to the Swift 3.0 milestone Aug 12, 2016
@jrose-apple
Copy link
Contributor Author

@swift-ci Please test

@tkremenek tkremenek self-assigned this Aug 12, 2016
@jrose-apple
Copy link
Contributor Author

jrose-apple commented Aug 12, 2016

Failed in LLDB tests on Linux (for unrelated reasons, I believe).

@tkremenek tkremenek merged commit e9cbb6f into swiftlang:swift-3.0-branch Aug 12, 2016
@jrose-apple jrose-apple deleted the swift-3-inout-ambiguity branch August 12, 2016 15:39
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.

2 participants