-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Sema: Fix order dependency in @objc inference from witnessed protocol requirement #24255
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
slavapestov
merged 1 commit into
swiftlang:master
from
slavapestov:objc-from-witnessed-requirement-ordering
Apr 25, 2019
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
31 changes: 31 additions & 0 deletions
31
test/decl/protocol/conforms/objc_from_witness_corner_case.swift
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
// RUN: %target-swift-frontend -disable-objc-attr-requires-foundation-module -print-ast %s | %FileCheck %s | ||
|
||
// REQUIRES: objc_interop | ||
|
||
// This bug required an elaborate setup where isObjC() was checked prior | ||
// to validateDecl() getting called on a declaration. In this case, we | ||
// did not infer @objc from witnessed protocol requirements as required. | ||
// | ||
// https://bugs.swift.org/browse/SR-10257 | ||
|
||
@objc public protocol P { | ||
@objc optional func f() | ||
} | ||
|
||
public class Other { | ||
// This triggers a walk over all nominals in the file, collecting | ||
// @objc members into the dynamic dispatch lookup table. | ||
let a = (Base() as AnyObject).g() | ||
} | ||
|
||
@objc public class Base : P { | ||
@objc public func g() -> Int { return 0 } | ||
} | ||
|
||
public class D : Base { | ||
// This method witnesses P.f() and so it should be @objc. | ||
// | ||
// CHECK-LABEL: @objc public func f() | ||
public func f() {} | ||
} | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment seems like it shouldn't be correct. Either this function is called re-entrantly and will loop infinitely because of the above call, or the above call notices the circularity and returns without setting anything up. If you're talking about the latter, maybe this should move inside the first
if
to make it clearer what's going on?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, it's not this function that's called re-entrantly; the bad case is when validateDecl() calls us, and we call validateDecl(). In this case validateDecl() returns without doing anything.