<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 class="">I still thing that the naming is one of the hardest parts:</div><div class="">Imho "@super" just feels wrong — the word has already a meaning, and it should only be used when referring to the parent class (here, it is a restriction/hint for subclasses).</div><div class="">The best I can think of would be @extend (because it is about extension of the marked method)</div><div class=""><br class=""></div>I definitely support the idea in general, so I've something to add:<div class="">— There are already cases where super shouldn't be called (<b class="">never</b>?)</div><div class=""><div class="">— Imho <b class="">before</b> and <b class="">after</b> only make sense if the call to super is generated automatically when it is omitted: The restriction on the order afaics offers very little (if any) additional safety, and it isn't clear how <i class="">defer</i> would interact with <b class="">before</b>.</div></div><div class=""><br class=""></div><div class="">Some questions that should imho be addressed in a formal proposal:</div><div class="">What about parameters and return values? Should it be possible to change those? I think so, but that would make the feature more dangerous than pure monitoring. If it's forbidden to change anything, we loose flexibility, and if it's configurable, complexity is raised.</div><div class=""><br class=""></div><div class="">- Tino</div></body></html>