Skip to content

[libdispatch-fixits] Address stale or incorrect fixits #3635

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
Jul 21, 2016
Merged

[libdispatch-fixits] Address stale or incorrect fixits #3635

merged 1 commit into from
Jul 21, 2016

Conversation

mwwa
Copy link
Contributor

@mwwa mwwa commented Jul 20, 2016

What's in this pull request?

Fixes to fixits presented regarding old Dispatch API

Resolved bug number:

    <rdar://problem/26681271>
    <rdar://problem/27088581>
    <rdar://problem/27181502>

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.

    * Several fixits references stale or deprecated methods, or
    generated incorrect syntax when applied to actual code.

    Fixes:
	<rdar://problem/26681271>
	<rdar://problem/27088581>
	<rdar://problem/27181502>
@mwwa
Copy link
Contributor Author

mwwa commented Jul 20, 2016

@swift-ci please test

@mwwa
Copy link
Contributor Author

mwwa commented Jul 20, 2016

@DougGregor Can you review?

public func dispatch_queue_create(_ label: UnsafePointer<Int8>?, _ attr: __OS_dispatch_queue_attr?) -> DispatchQueue
{
fatalError()
}

@available(*, unavailable, renamed:"DispatchQueue.init(label:attributes:target:)")
@available(*, unavailable, renamed:"DispatchQueue.init(label:qos:attributes:autoreleaseFrequency:target:)")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if this one will actually produce working Fix-Its, because the # of arguments doesn't match up, but it will still give a reasonable diagnostic.

@DougGregor
Copy link
Member

The Intents failure is a separate issue. LGTM!

@DougGregor DougGregor merged commit 9575215 into swiftlang:master Jul 21, 2016
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