The Surprising Cost of Protocol Conformances in Swift

I feels like I must be missing something. 3ms is extremely slow. Surely it should be 3us, no? What’s it doing that is so slow?

<p><pre><code> &gt; The concept behind zconform is to eagerly load all possible protocol conformances and store them in a map keyed by the protocol’s address in memory. </code></pre> if it works well in most scenarios, couldn&#x27;t this just be implemented directly in the swift runtime at some point?

This is about the casting cost specifically, not the direct cost of using a protocol as interface, which itself has some annoying performance characteristics

Swift has a real performance problem, it doesn&#x27;t seem competitive with other &quot;systems languages&quot;<p>Is the goal to make it faster later? What can be done to get closer to that goal?