-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Sema: Don't complain about internal type aliases referenced from @inlinable functions in Swift < 4.2 #17493
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:muffle-another-inlinable-warning
Jun 26, 2018
Merged
Sema: Don't complain about internal type aliases referenced from @inlinable functions in Swift < 4.2 #17493
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
// RUN: %target-typecheck-verify-swift -swift-version 4 | ||
|
||
// No diagnostics at all in Swift 4.0 mode. | ||
|
||
private typealias PrivateAlias = Int | ||
|
||
internal typealias InternalAlias = Int | ||
|
||
@usableFromInline typealias UsableFromInlineAlias = Int | ||
|
||
public typealias PublicAlias = Int | ||
|
||
@inlinable public func f() { | ||
_ = PrivateAlias.self | ||
|
||
_ = InternalAlias.self | ||
|
||
_ = UsableFromInlineAlias.self | ||
|
||
_ = PublicAlias.self | ||
} |
4 changes: 3 additions & 1 deletion
4
...patibility/attr_inlinable_typealias.swift → ...ty/attr_inlinable_typealias_swift42.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
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.
Hm. :-/ What happens in Swift 4.0 mode when Swift 5 come out?
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.
I’m not sure I follow?
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.
I thought the reason we were adding these warnings is because they could lead to linker errors in Swift 5. Maybe I'm misremembering.
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.
They can lead to linker errors in any release. Here is a test case:
In 4.1, this produced no warning and failed to link when another module inlined f(). In Swift 5 mode this is an error. In 4.2 it's just a warning.
The reason it's just a warning is because there are valid code patterns you can write too, eg the underlying type of the Alias is
@usableFromInline
:The correct way to write the above is to write, the following, which is the only variant that compiles without errors in Swift 5 mode:
However, in Swift 4.1,
@usableFromInline
was not allowed on type aliases at all. SwiftNIO wants to have the same source compile warning-free on both 4.1 and 4.2. So they're just not declaring their type aliases as@usableFromInline
and promising to ensure the underlying type has the right visibility.Once 4.2 is GM, I expect they will drop support for 4.1, and I will go back to emitting these warnings unconditionally. (And in Swift 5 mode it's an error as always).
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.
Thanks for the explanation.