Skip to content

[Import as Member] Inferred inits are factory #4335

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 19, 2016

Conversation

milseman
Copy link
Member

What's in this pull request?

Prior to this, developers could run into trouble if they defined their own init that called a inferred-import-as-member factory init, because we were not adequately setting the factory-ness.

Resolved bug number: (SR-)


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.

Inferred inits from C via import-as-member are factory inits, so treat
them as such. Core Graphics test case included.

@milseman
Copy link
Member Author

@swift-ci please test

@@ -2564,6 +2564,10 @@ auto ClangImporter::Implementation::importFullName(
else if (inference.isSetter())
result.AccessorKind = ImportedAccessorKind::PropertySetter;

// Inits are factory
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you beef up this comment to explain why we need this?

@milseman
Copy link
Member Author

Linux failure seems unrelated. I will update PR with better comments.

Inferred inits from C via import-as-member are factory inits, so treat
them as such. Core Graphics test case included.
@milseman
Copy link
Member Author

@swift-ci please smoke test

@milseman
Copy link
Member Author

Update was comment only, so just smoke test to gate PR

@tkremenek
Copy link
Member

@swift-ci test

@slavapestov
Copy link
Contributor

I think this should go into master, even if it is not a complete fix for the issue. Once we add factory init support to SILGen, this change will be a pre-requisite anyway.

@milseman
Copy link
Member Author

Why can't I see the builder status?

@jrose-apple
Copy link
Contributor

It's been buggy lately. You can usually find it at https://ci.swift.org/view/Pull%20Request/, but then you'll have to get an admin to force-merge it (Ted or Ewa).

@milseman
Copy link
Member Author

Anywho, this passed a long time ago, and the only change was to a comment. It should be merge worthy.

@tkremenek or @ematejska , do you want to run this through smoke test or merge?

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.

5 participants