You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
swift-ci opened this issue
Jun 19, 2016
· 3 comments
Assignees
Labels
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfcrashBug: A crash, i.e., an abnormal termination of software
When a protocol declares an optional variable, and an implementer implements that variable as a lazy initialised one, the compiler will produce a Segmentation Fault 11. Changing the declaration to a non-lazy declaration will not fail to build
A demo playground is attached, this produces the problem in an implementation on UIApplicationDelegate, and a complete protocol/implementation pair.
Here is a log from another project which produces the same error.
This happens in XCode 8.3.2 when trying to lazy init the TwitterKit client. I am not sure if it is an optional var in a protocol or not, I think not...
Will crash: lazy var twitter: TWTRAPIClient = TWTRAPIClient.init(userID: Twitter.sharedInstance().sessionStore.session()!.userID)
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfcrashBug: A crash, i.e., an abnormal termination of software
Attachment: Download
Environment
Version 8.0 beta (8S128d)
Swift 3.0
Additional Detail from JIRA
md5: 74584a9fc98466ac7aa296efa6be8ec7
Issue Description:
When a protocol declares an optional variable, and an implementer implements that variable as a lazy initialised one, the compiler will produce a Segmentation Fault 11. Changing the declaration to a non-lazy declaration will not fail to build
A demo playground is attached, this produces the problem in an implementation on UIApplicationDelegate, and a complete protocol/implementation pair.
Here is a log from another project which produces the same error.
The text was updated successfully, but these errors were encountered: