<div dir="ltr">I'm not very familiar with the runtime so forgive me – the protocols would only have to be added once right? And couldn't this usually be done at compile time, or does it happen when the module is linked at startup?</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 4, 2016 at 4:36 PM, Haravikk via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
> On 4 Aug 2016, at 03:19, Brent Royal-Gordon via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
><br>
>> On Aug 3, 2016, at 10:17 AM, Manav Gabhawala via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
>><br>
>> I was wondering why this would put any more of a burden on the runtime<br>
>> than simple inheritance of protocols. The way this could be<br>
>> implemented is to augment the ConformanceTable for nominal types by<br>
>> looking up its protocol extension’s inheritance clauses. I can<br>
>> definitely see this impacting compile time but I don’t see why runtime<br>
>> performance will be any different than simple inheritance. Further,<br>
>> cyclic chains can be detected and broken (compiler error) during the<br>
>> second pass of semantic analysis.<br>
><br>
> My understanding—which may be incorrect, by the way—is that the issue is mainly with protocol extensions adding conformances, not specifically with those conformances being conditional, and that it specifically has to do with `is` and `as?` checks across module boundaries.<br>
><br>
> Suppose you have these declarations in module M:<br>
><br>
> public protocol AProtocol {…}<br>
> public protocol BProtocol: AProtocol {…}<br>
> public protocol CProtocol {…}<br>
><br>
> // Public or otherwise doesn't matter here.<br>
> public struct Foo: BProtocol {…}<br>
><br>
> Foo essentially has a flat list of the protocols it conforms to attached to it. Notionally, you can think of that list as looking like:<br>
><br>
> Foo.self.conformsTo = [BProtocol.self, AProtocol.self]<br>
><br>
> And when you write `foo is CProtocol`, that eventually translates into:<br>
><br>
> foo.dynamicType.conformsTo.<wbr>contains(CProtocol.self)<br>
><br>
> For a `Foo`, since the `conformsTo` list doesn't include `CProtocol.self`, it returns `false`.<br>
><br>
> Now imagine that you write a new module, N, and in it you say:<br>
><br>
> extension Foo: CProtocol {…}<br>
><br>
> You have now retroactively conformed `Foo` to `CProtocol`. Swift needs to reach into module M and add `CProtocol.self` to the `Foo.self.conformsTo` list. This is perfectly doable for a concrete type—it's one flat list, after all.<br>
><br>
> Instead, though, imagine that module N extended `AProtocol` to add a conformance:<br>
><br>
> extension AProtocol: CProtocol {…}<br>
><br>
> There are two ways to handle this. One is to find all types conforming to `AProtocol`, recursively, and add `CProtocol.self` to their conformance list. The other is to scrap the flat list of conformances and instead make `is` and `as?` recursively search each protocol. Either way, you have replaced a fast, flat operation with a slow, recursive one.<br>
><br>
> Conditional conformance adds another wrinkle to this, of course—you must not only recursively search the list, but also evaluate the condition to see if it applies in this case. But the general problem of having to replace a fast search with a slow search applies either way.<br>
<br>
</div></div>Great explanation! This switch from flat to recursively searched though seems like it would only occur when the extension is in an external module though; for internal modules would it not still be possible to determine the flat list for each type? In that case extending a type from another module could be either disallowed, or produce a warning to indicate the performance implication?<br>
<br>
The feature would still be very useful even just for internal use after all. Also it seems useful on a relatively small number of types, and the number of external modules that need/want to do this must narrow that even further, so external extensions may be quite niche, i.e- not worth losing the feature for internal use if that is indeed easier?<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
</div></div></blockquote></div><br></div>