> Frankly, I think having `final` in the language at all is a mistake. While I
> agree that we should prefer composition to inheritance*, declaring things
> final is hubris. The only reasonable use case I've seen is for optimization,
> but that smacks of developers serving the compiler rather than the converse.
> Bringing an analog of NS_REQUIRES_SUPER to Swift would be most welcome;
> that's as far as I'd go down the path of dictating framework usage.
I really like the direction this discussion has taken ;-):
Is there any counter argument beside performance (which imho should always be
seen under the aspect of premature optimization) that speaks against making
NS_REQUIRES_SUPER the default behavior?
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
