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
[SR-11074] Segmentation fault 11 Xcode 11 beta 3 #53466
Comments
Any compiler crash is a bug, so thank you for filing! |
@DougGregor, @xedin, does this look familiar? dasoga (JIRA User), do you have a self-contained test case? |
Comment by Dante Solorio (JIRA) Not really @belkadan |
Even if you could share your project, it would help. As is, you haven't shared the code that actually crashes, and the protocol references types that are outside the code you did share. |
Comment by Dante Solorio (JIRA) Ok @belkadan I just attached the whole library. Thanks for your help. |
Thank you! @swift-ci create |
Reduced the project down to: // These typealiases just represent types that can be arbitrary as long as they
// line up. Set them to any type you want, or substitute them, and it'll still
// reproduce.
typealias T1 = Int
typealias T2 = Float
typealias T3 = Bool
protocol DexCommand {
associatedtype ResultType
static var operationFactory: (T1, (ResultType) -> T2) { get }
}
extension DexCommand {
static func bind() -> (T1, (ResultType) -> T2) {
fatalError()
}
}
struct TestVIUSignalStrength: DexCommand {
typealias ResultType = T3
static let operationFactory: (T1, (ResultType) -> T2) = bind()
} The dependencies and project configuration don't matter—this will reproduce on the command line with |
Attachment: Download
Environment
macOC Mojave (10.14.5)
Xcode Version 11.0 beta 3 (11M362v)
Library is in Swift 4
Additional Detail from JIRA
md5: 7e389cbe60ee9ec6c8eaefa2e0b9f9fc
duplicates:
Issue Description:
Segmentation fault: 11 Xcode 11 beta 3
I updated Xcode 11 beta 2 to beta 3 and I got a compiler crash with legacy library.
Can somebody help me to identify if this is a bug in this beta? thanks in advance
I have this protocol:
This is the stack:
The text was updated successfully, but these errors were encountered: