<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hey, and welcome!<div class=""><br class=""></div><div class="">We actually talked about it some time before Christmas, with possible names like @must_override. The talks seemed to be going well, but I haven't been following the discussion closely, so cannot provide a summary or status, unfortunately. Please try to find it in the archives.</div><div class=""><br class=""></div><div class="">A.</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 15, 2016, at 6:38 AM, Nate Birkholz via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">My first ever post on this list or any open source project, sorry if I'm not following procedure accurately, here.</div><div class=""><br class=""></div><div class="">Currently, the "required" keyword on an initializer causes subclasses to implement their own init methods in place of the so-marked initializer. I propose extending the use of the required keyword to methods such that when a new subclass is created, it must create its own unique implementation of the method, or at ;east explicitly invoke the superclass implementation via super.methodName()</div><div class=""><br class=""></div><div class="">Requiring child classes to implement the method will improve the maintainability of codebases over time and is a logical extension of the current implementation on initialization. This will provide a useful, nondisruptive, nonbreaking communication tool.</div><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature">Nate Birkholz</div>
</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=LRtxqIpN0uduUbaiFaLozLZv7i-2BSLNOBgkrlBNK2PSXQdC0eprn8rgToVGT4HlNxjGcbXSyOsxztB7XUq1a8H7ufqaCXxz-2FSJ9q8FAhkgEzd3Nnzj6YzfRu827UpksA902Of1usI3XYC02Vjfpa0NPwZsEObTtStMVLgJwt6w5QpKPJG3JDKKohr49m1eT6uKNju5v2k-2FmwnTqwd4WSFgq9-2BvWRCDaR85Alb8nyEmwk-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></body></html>