<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">When methods are overriden, design often requires that the super implementation be called, sometimes even at a specific time (before / after the new implementation). Should this change also provide support for this sort of pattern, or would that be beyond the scope? (Note that this was possible in Obj-C with<span class="Apple-converted-space"> </span><i class="">NS_REQUIRES_SUPER</i>)</div></div></blockquote></div>Imho something like this would be way better than „willSet/didSet“, which introduces a bunch of new keywords and is only usable for properties.<div class="">Declaring everything final by default sounds good in theory, but I think in reality, it will just make things complicated in most cases — and beside more options for the compiler to optimize, I don’t see any benefit in forbidding a subclass to be notified when one of its inherited methods gets called.</div><div class="">So, I would vote for NS_REQUIRES_SUPER to be the default (because it doesn’t hurt in most cases, and it’s so hard to find a proper keyword for that behavior ;-)</div></body></html>