<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 Nov 27, 2017, at 2:56 AM, Tino Heth <<a href="mailto:2th@gmx.de" class="">2th@gmx.de</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; line-break: after-white-space;" class=""><div class=""><br class=""><blockquote type="cite" class=""><div class=""><span 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; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">The implementation is straight-forward and (IMO) non-invasive in the compiler.</span><br 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; -webkit-text-stroke-width: 0px;" class=""></div></blockquote></div>At least it’s smaller than I would have expected — but I don’t have the overview to judge the consequences to the compiler.<div class=""><br class=""></div><div class="">However, the impact those two proposals have on Swift is imho huge, and as the whole story is quite special for several reasons, there’s an elephant in the room that shouldn’t be ignored:</div><div class="">- What would you do if the proposal isn’t accepted?</div></div></div></blockquote><div><br class=""></div><div>Circle back and try to solve the problem another way? It depends on why it would be rejected.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">- What does core think you would do in this case?</div></div></div></blockquote><div><br class=""></div><div>The core team officially weighs in after the review process, not before.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">- What impact will that speculation have on the decision?</div></div></div></blockquote><div><br class=""></div><div>It should be zero. The point of the review process is to weigh the merits of a proposal.</div><br class=""></div><div>In any case, FWIW, I don’t find your email very helpful, since you’re not actually talking about technical merits of the proposal: you’re encouraging speculation about politics :-)</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>