Skip to content

[Parse] Add fix-its for empty Swift 2 operator decl braces. #4309

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 1 commit into from
Aug 15, 2016

Conversation

jrose-apple
Copy link
Contributor

@jrose-apple jrose-apple commented Aug 15, 2016

And improve the error message for non-empty braces; if we're going to ignore the contents, we should at least point you in the right direction for Swift 3.

This comes from SE-0077: Improved operator declarations.

rdar://problem/27576922


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.

And improve the error message for non-empty braces; if we're going to
ignore the contents, we should at least point you in the right
direction for Swift 3.

rdar://problem/27576922
@jrose-apple
Copy link
Contributor Author

@swift-ci Please smoke test

@jrose-apple
Copy link
Contributor Author

@akyrtzi, @nkcsgexi, or @rjmccall, can you review this?

@rjmccall
Copy link
Contributor

LGTM.

@nkcsgexi
Copy link
Contributor

Thanks for adding this! Is empty brace a typical use-pattern for operator declarations?

@jrose-apple
Copy link
Contributor Author

In Swift 2 all operator decls had braces, but prefix and postfix operators never had anything in them, ever. Infix operators used to have the information that's now in precedence groups.

(I'm a little unhappy that we just throw that information away, but that would be a bigger issue to fix.)

@jrose-apple jrose-apple merged commit 3d005f3 into swiftlang:master Aug 15, 2016
@jrose-apple jrose-apple deleted the braceless-operators branch August 15, 2016 21:43
jrose-apple added a commit to jrose-apple/swift that referenced this pull request Aug 15, 2016
…g#4309)

And improve the error message for non-empty braces; if we're going to
ignore the contents, we should at least point you in the right
direction for Swift 3.

rdar://problem/27576922
(cherry picked from commit 3d005f3)
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants