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><div class="gmail_quote"><div dir="ltr">On Thu, Sep 7, 2017 at 14:32 Gwendal Roué 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"><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>Le 7 sept. 2017 à 19:53, Tony Allevato <<a href="mailto:tony.allevato@gmail.com" target="_blank">tony.allevato@gmail.com</a>> a écrit :</div><br class="m_2957199913162527029Apple-interchange-newline"><div><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">Again, this is not the issue that Haravikk is describing in this thread.</div></div></blockquote><br></div></div><div style="word-wrap:break-word"><div>Yes, I better understand now. Please forgive the pollution.</div></div><div style="word-wrap:break-word"><div><br></div><div>Gwendal</div><div><br></div></div>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>