<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><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 class="">- What does core think you would do in this case?</div><div class="">- What impact will that speculation have on the decision?</div><div class=""><div class="">I can’t see what’s happening behind the scenes (basically, everything beyond the ML), but those non-technical questions might have a big impact if people construct their own narratives.</div></div><div class=""><br class=""></div><div class="">Besides that general concern, I think the whole „dynamic Swift“ topic shouldn’t be rushed:</div><div class="">How about keeping it in a public branch, so that users of script languages (not only Python) can play with it, and use that experience to decide the question in the Swift 6 timeframe?</div></body></html>