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
The attached project (also https://github.com/dabrahams/CrossModuleConformance) demonstrates that Swift's semantics around conformances and multiple modules are nondeterministic, if not insane. I've never found any documentation of how this is supposed to work, and the explanations I've heard from people have always been vague at best. Somebody needs to write down what is supposed to be happening, and then make the compiler do that!
The text was updated successfully, but these errors were encountered:
Just tested with Swift 5.2.4 and all the insanity appears to be gone except for the availability of idA without importing A in Test3, which is not about conformances, but which persists.
Attachment: Download
Additional Detail from JIRA
md5: bff8be030eae13e3fbbaaf365faacf69
Issue Description:
The attached project (also https://github.com/dabrahams/CrossModuleConformance) demonstrates that Swift's semantics around conformances and multiple modules are nondeterministic, if not insane. I've never found any documentation of how this is supposed to work, and the explanations I've heard from people have always been vague at best. Somebody needs to write down what is supposed to be happening, and then make the compiler do that!
The text was updated successfully, but these errors were encountered: