<div dir="ltr"><span style="font-size:12.8px">* What is your evaluation of the proposal?</span><div><br></div><div>Strong support.</div><div><br style="font-size:12.8px"><span style="font-size:12.8px">* Is the problem being addressed significant enough to warrant a change to Swift?</span></div><div><br></div><div>Yes. Language-level support for bridging between a certain fixed set of Objective-C and Swift types is surprising behavior, especially since no other dynamic conversions between otherwise-unrelated types using the casting keywords are supported by Swift.</div><div><br style="font-size:12.8px"><span style="font-size:12.8px">* Does this proposal fit well with the feel and direction of Swift?</span></div><div><br></div><div>Very much so. It removes language features that don't have a compelling reason to exist and replaces them with library initializers that have the same level of expressiveness. And it is a more sound engineering decision than the other principled alternative - to open up the dynamic conversion machinery to allow user-defined conversions.</div><div><br style="font-size:12.8px"><span style="font-size:12.8px">* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</span></div><div><br></div><div>None. Swift's interoperability story with Objective-C is (to my knowledge) unprecedented - it is far more involved than (e.g.) Scala interoperating with Java. The core team has clearly been tracking what works and what doesn't and making necessary changes as they present themselves, and this is yet another along that path.</div><div><br style="font-size:12.8px"><span style="font-size:12.8px">* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span><br></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Carefully read through the proposal. Considered usage of 'as' and 'as?' in prior projects, especially in code requiring bridging to/from NSDictionaries. Read through the related threads.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Best,</span></div><div><span style="font-size:12.8px">Austin</span></div><div><span style="font-size:12.8px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 10, 2016 at 11:53 AM, Chris Lattner via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Swift community,<br>
<br>
The review of "SE-0083: Remove bridging conversion behavior from dynamic casts" begins now and runs through May 16. The proposal is available here:<br>
<br>
<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0083-remove-bridging-from-dynamic-casts.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0083-remove-bridging-from-dynamic-casts.md</a><br>
<br>
Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at<br>
<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>
<br>
or, if you would like to keep your feedback private, directly to the review manager.<br>
<br>
What goes into a review?<br>
<br>
The goal of the review process is to improve the proposal under review through constructive criticism and contribute to the direction of Swift. When writing your review, here are some questions you might want to answer in your review:<br>
<br>
* What is your evaluation of the proposal?<br>
* Is the problem being addressed significant enough to warrant a change to Swift?<br>
* Does this proposal fit well with the feel and direction of Swift?<br>
* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
<br>
More information about the Swift evolution process is available at<br>
<br>
<a href="https://github.com/apple/swift-evolution/blob/master/process.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a><br>
<br>
Thank you,<br>
<br>
-Chris Lattner<br>
Review Manager<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">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><br></div>