<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="">What if we tried a completely different type of solution (which might solve the issue for protocol default conformances too)?<div class=""><br class=""></div><div class="">Right now there are errors and warnings. What if we add a third type of compiler feedback (let’s call it a note). A note is a little bit like a warning, but it can be dismissed/acknowledged. It is only generated once for a particular issue, and then it is remembered that you dismissed it so it won’t come back every time you compile.</div><div class=""><br class=""></div><div class="">So in this case, when you add an Equatable conformance post-hoc, you get a note (let’s say it looks like a warning, but is grey instead of yellow and has a different icon) saying something like “Equatable conformance was automatically synthesized”. If you want to remember to add your own conformance, you can just leave the note there as a reminder to yourself until you do it. If you want the automatic conformance then you just dismiss the note and it never bothers you again.<br class=""><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Jon</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 7, 2017, at 12:52 PM, Xiaodi Wu 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="">This is a particularly interesting use case that demonstrates a weakness without a good workaround. I, for one, am glad you brought it up, and agree with comments above that auto-generated mandatory enum conformance is a topic perhaps worth revisiting, given this compelling example.<br class=""><div class="gmail_quote"><div dir="ltr" class="">On Thu, Sep 7, 2017 at 14:32 Gwendal Roué via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">Le 7 sept. 2017 à 19:53, Tony Allevato <<a href="mailto:tony.allevato@gmail.com" target="_blank" class="">tony.allevato@gmail.com</a>> a écrit :</div><br class="m_2957199913162527029Apple-interchange-newline"><div class=""><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">Again, this is not the issue that Haravikk is describing in this thread.</div></div></blockquote><br class=""></div></div><div style="word-wrap:break-word" class=""><div class="">Yes, I better understand now. Please forgive the pollution.</div></div><div style="word-wrap:break-word" class=""><div class=""><br class=""></div><div class="">Gwendal</div><div class=""><br class=""></div></div>_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</blockquote></div>
_______________________________________________<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></div></body></html>