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
Sep 14, 2016
· 3 comments
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
I'm guessing that calling a private type in an `@objc` qualified function makes it access control level changed, and since there two private `PrivateStruct` defined in `NSView` and both called in an `@objc` qualified function, so they are collided with each other by itself's name during the compiling.
We need some way to disambiguate the two private types in our mangling, and then a way to recover that difference when we look them up later. Failing that, we should reject this code for now.
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
OS X 10.11
iOS 10
Xcode 8.0 (8A218a)
Additional Detail from JIRA
md5: 28edbd025d39c8d19d8ae3cd298fc229
is duplicated by:
relates to:
Issue Description:
With following code, we can get a Segmentation Fault 11 during the compiling.
I'm guessing that calling a private type in an `@objc` qualified function makes it access control level changed, and since there two private `PrivateStruct` defined in `NSView` and both called in an `@objc` qualified function, so they are collided with each other by itself's name during the compiling.
We can change the code to be:
And at this time, the Segmentation Fault 11 has gone.
The text was updated successfully, but these errors were encountered: