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
Apologies if this is being filed in the wrong place.
I'd expect both implementations to behave the same way. However, implementation 1 never calls the method in class B. Noticed this when porting my project to swift 3.
I tried to simplify the example more by providing my own protocol and "table" class, but I couldn't get it to behave the same way again. This leads me to believe that the observed behavior in this example is not expected and actually a bug.
The text was updated successfully, but these errors were encountered:
This appears to have been regressed in Swift 5. See linked SO post for more information by several people that have ran into this: https://stackoverflow.com/a/55393950/1943064 . The issue randomly appears and goes away when making changes to the affected file. Once built however, the issue either persists 100% of the time or doesn't exist at all, so it has to be a compile time issue. I've had instances where one subclass was affected and other wasn't. This is pretty serious as swift 5 is deemed production ready.
Additional Detail from JIRA
md5: a8e5045579f682f39718f2d78d858e23
Issue Description:
Apologies if this is being filed in the wrong place.
I'd expect both implementations to behave the same way. However, implementation 1 never calls the method in class B. Noticed this when porting my project to swift 3.
I tried to simplify the example more by providing my own protocol and "table" class, but I couldn't get it to behave the same way again. This leads me to believe that the observed behavior in this example is not expected and actually a bug.
The text was updated successfully, but these errors were encountered: