[swift-evolution] Static Dispatch Pitfalls

Brent Royal-Gordon brent at architechies.com
Sat May 21 16:50:05 CDT 2016

> Making them 'final' causes problems with retroactive modeling.

Because of that issue, I had an attribute you could use to acknowledge conflicts and disable the error. But this ended up being rather complex: you needed to be able to label a member *or* an extension *or* an import which made a conflicting member and conformance visible in the same place.

Here's the last draft of the proposal, from way back in December: <https://github.com/brentdax/swift-evolution/blob/final-protocol-methods/proposals/0000-require-final-on-protocol-extension-methods.md>

Brent Royal-Gordon

More information about the swift-evolution mailing list