<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Jun 5, 2017, at 12:08 AM, Jens Persson via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div dir="ltr" class="">So the bug in the reflective type system needs to be fixed before SE-0110 can actually be implemented (so that the statements in its title and text are true when compared to the actual behavior of the current Swift 4 compiler), </div></div></blockquote><div><br class=""></div>Gaps in the reflective type system are bugs, but they are not showstopper bugs. We do not even expose any way to query the reflective system today; it basically only affects type equality and dynamic casts that programmers are very unlikely to use. The changes in call type-checking are vastly more important, are implemented (modulo bugs, of course), and by themselves warrant calling SE-0110 implemented.</div><div><br class=""></div><div>John.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">And yet:</div><div class=""><br class=""></div><div class="">1. The status of SE-0110 is "Implemented"</div><div class=""><br class=""></div><div class="">2. These statuses of the following issues are "resolved":</div><div class=""> SR-2008: Distinguish between single-tuple and multiple-argument function types<br class=""></div><div class=""> SR-2216: Confusing behavior related to closure types and tuples</div><div class=""> SR-296: Fix inconsistencies related to tuples, arg/param lists, type params, typealiases</div><div class=""><br class=""></div><div class="">Why?</div><div class=""><br class=""></div><div class="">/Jens</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sun, Jun 4, 2017 at 5:49 PM, Ben Rimmington <span dir="ltr" class=""><<a href="mailto:me@benrimmington.com" target="_blank" class="">me@benrimmington.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I assumed that Swift 3 mode would be the default, so that existing `#!/usr/bin/swift` scripts continue to work.<br class="">
<span class="HOEnZb"><font color="#888888" class=""><br class="">
-- Ben<br class="">
</font></span><div class="HOEnZb"><div class="h5"><br class="">
> On 3 Jun 2017, at 23:47, Jens Persson <<a href="mailto:jens@bitcycle.com" class="">jens@bitcycle.com</a>> wrote:<br class="">
><br class="">
> Yes of course, try my demonstration code yourself.<br class="">
> (In the current dev snapshots, -swift-version 4 is the default and -swift-version 3 is what you need to set if you want 3 compability)<br class="">
><br class="">
>> On Sun, Jun 4, 2017 at 12:37 AM, Ben Rimmington <<a href="mailto:me@benrimmington.com" class="">me@benrimmington.com</a>> wrote:<br class="">
>><br class="">
>> Are you using the Swift 4 language mode?<br class="">
>><br class="">
>> <<a href="https://swift.org/blog/swift-4-0-release-process/#source-compatibility" rel="noreferrer" target="_blank" class="">https://swift.org/blog/swift-<wbr class="">4-0-release-process/#source-<wbr class="">compatibility</a>><br class="">
>><br class="">
>> -- Ben<br class="">
</div></div></blockquote></div><br class=""></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=""></body></html>