<div dir="ltr"><span style="color:rgb(33,33,33);font-family:"helvetica neue",helvetica,arial,sans-serif;font-size:13px">+1. This is the cleanest proposed solution I've seen to this problem. Like many people, I've started breaking up a lot of my large classes like view controllers that have multiple protocol conformances into separate extensions, and this would let many of those diagnostics fall out naturally.</span><div><font color="#212121" face="helvetica neue, helvetica, arial, sans-serif"><br></font><br><div class="gmail_quote"><div dir="ltr">On Tue, Sep 20, 2016 at 7:50 AM Martin Waitz via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello everybody,<br class="gmail_msg">
<br class="gmail_msg">
Several suggestions are floating around about explicitly marking a<br class="gmail_msg">
method to implement a protocol requirement.<br class="gmail_msg">
<br class="gmail_msg">
E.g.:<br class="gmail_msg">
<br class="gmail_msg">
> class Foo : Bar {<br class="gmail_msg">
> implement func foo() {...}<br class="gmail_msg">
> }<br class="gmail_msg">
<br class="gmail_msg">
However, with extensions we can already do something very similar:<br class="gmail_msg">
<br class="gmail_msg">
class Foo {<br class="gmail_msg">
....<br class="gmail_msg">
}<br class="gmail_msg">
extension Foo: Bar {<br class="gmail_msg">
func foo() {...}<br class="gmail_msg">
}<br class="gmail_msg">
<br class="gmail_msg">
Maybe simply adding a new warning would already help.<br class="gmail_msg">
Extensions which introduce new protocol conformances could be reserved<br class="gmail_msg">
for those methods which are already defined within the protocol.<br class="gmail_msg">
Whenever such an extension contains an unrecognized method, we could<br class="gmail_msg">
issue a warning.<br class="gmail_msg">
Or maybe even an error, but we should allow private methods as an<br class="gmail_msg">
exception (for helper functions which are clearly not related to the<br class="gmail_msg">
protocol).<br class="gmail_msg">
<br class="gmail_msg">
This way, when the programmer wants to make sure that her new method is<br class="gmail_msg">
used by a protocol then she can simply put that method in an extension.<br class="gmail_msg">
<br class="gmail_msg">
--<br class="gmail_msg">
Martin<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div></div></div>