<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On 18 Sep 2017, at 9:46 am, Christopher Kornher <<a href="mailto:ckornher@me.com" class="">ckornher@me.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Sep 17, 2017, at 5:04 PM, BJ Homer <<a href="mailto:bjhomer@gmail.com" class="">bjhomer@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class="">Please note that, as proposed, enums are always treated as exhaustive *within the same module*. A new user writing MyFirstEnum is likely using it within the same module, and will thus get exhaustive behavior with no extra keywords required.<br class=""></div></div></blockquote><div class=""><br class=""></div><div class="">• What is your evaluation of the proposal?</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Uh, +1</div><div class=""><br class=""></div><div class=""> • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>not enough</div><div class=""><br class=""></div><div class="">Apologies for wasting everyone’s time…</div></div></div></div></blockquote><div><br class=""></div>Haha no problems. Yes, it seems clear people are jumping to conclusions. This is a case specifically for framework developers purely for interface consistency, with is *exactly* when you want the default behaviour to protect you from external dependency changes.</div><div><br class=""></div><div>Within the context of a single application at compile time, you will <b class="">always know</b> all cases already and therefore exhaustive can become the default. Cross frameworks, not so much.</div><div><br class=""><br class=""></div></body></html>