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-10271] Compiler crash during compilation #52671
Labels
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
compiler
The Swift compiler in itself
crash
Bug: A crash, i.e., an abnormal termination of software
regression
swift 5.0
type checker
Area → compiler: Semantic analysis
Comments
just pasting the whole code here as it's nice and short final class Binding<T> {
var currentValue: T
init(_ initial: T) {
currentValue = initial
}
}
extension Binding: ExpressibleByIntegerLiteral where T: ExpressibleByIntegerLiteral {
typealias IntegerLiteralType = T.IntegerLiteralType
convenience init(integerLiteral value: IntegerLiteralType) {
self.init(T(integerLiteral: value))
}
}
let binding = Binding(0) and the crasher
|
AnthonyLatsis
added
the
crash
Bug: A crash, i.e., an abnormal termination of software
label
Dec 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
compiler
The Swift compiler in itself
crash
Bug: A crash, i.e., an abnormal termination of software
regression
swift 5.0
type checker
Area → compiler: Semantic analysis
Attachment: Download
Environment
The Swift 5.0 compiler, macOS 10.14.4 using Xcode 10.2.
Additional Detail from JIRA
md5: def455ab1fe82f807ae0d9174b37af51
is duplicated by:
relates to:
Issue Description:
The attached code crashes during compilation. Removing the conditional conformance solved the compilation issues. Swift 4.2 compiler has no problems compiling this code, but the Swift 5 compiler does. Even when compiling Swift 4.2 modules using the Swift 5 compiler.
The text was updated successfully, but these errors were encountered: