Skip to content

Follow-up for fixing IDE/SourceKit tests after changes for [SE-0111] #4195

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 6 commits into from
Aug 10, 2016

Conversation

akyrtzi
Copy link
Contributor

@akyrtzi akyrtzi commented Aug 10, 2016

What's in this pull request?

Reviewed by Ben Langmuir.

These are changes for fixing fallout on IDE/SourceKit after changes related to [SE-0111].
The changes are intrusive but they fix critical problems, for example failing to show external argument names in code-completion or cursor-info not showing local parameter names in function types.

Resolved bug number: (SR-)

rdar://27642873


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.

Also fixup 'test/SourceKit/CodeExpand/code-expand.swift' and use the syntax
for adding parameter names with an underscore for first name.
- Make sure VarDecls have an associated TypeLoc, like ParamDecls do, then use it for printing the VarDecl's type.
This is done by moving ParamDecl's TypeLoc up to the VarDecl.
This is useful for being able to display the parameter names of function types embedded in VarDecls.

- Use the result TypeLoc of functions for printing. This enables printing parameter names of function types embedded in return types.

- Make sure to annotate attributes while they are printed.
@akyrtzi
Copy link
Contributor Author

akyrtzi commented Aug 10, 2016

@swift-ci smoke test OS X platform

@akyrtzi
Copy link
Contributor Author

akyrtzi commented Aug 10, 2016

@swift-ci test OS X platform

@akyrtzi akyrtzi added this to the Swift 3.0 milestone Aug 10, 2016
@akyrtzi
Copy link
Contributor Author

akyrtzi commented Aug 10, 2016

test/IDE/complete_from_stdlib.swift fails because of a stdlib difference between the branches, will update the test.

@akyrtzi
Copy link
Contributor Author

akyrtzi commented Aug 10, 2016

@swift-ci test OS X

@shahmishal
Copy link
Member

@swift-ci test OS X platform

@ematejska ematejska merged commit 31700c7 into swiftlang:swift-3.0-branch Aug 10, 2016
@akyrtzi akyrtzi deleted the se-0111-followup-swift3 branch August 10, 2016 20:40
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.

4 participants