<div>        <font size="2"><span style="background-color:rgba(255,255,255,0)">• What is your evaluation of the proposal?<br></span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)">Good idea, it gets rid of compiler magic</span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></div><div>        <font size="2"><span style="background-color:rgba(255,255,255,0)">• Is the problem being addressed significant enough to warrant a change to Swift?<br></span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)">Yes, plenty of mixed projects. Plenty of Cocoa libraries that could be improved with a Swift API. </span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></div><div>        <font size="2"><span style="background-color:rgba(255,255,255,0)">• Does this proposal fit well with the feel and direction of Swift?<br></span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)">Yes, obj-c is still important </span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></div><div>        <font size="2"><span style="background-color:rgba(255,255,255,0)">• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br></span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)">No, but have wanted this in Swift</span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></div><div>        <font size="2"><span style="background-color:rgba(255,255,255,0)">• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></div><div><font size="2"><span style="background-color:rgba(255,255,255,0)">Followed discussions on swift-evolution <span></span></span></font></div><div><br></div><br>On Tuesday, 5 April 2016, Joe Groff via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hello Swift community,<br><br>The review of “Allow Swift types to provide custom Objective-C representations” begins now and runs through April 11, 2016. The proposal is available here:<br><br><span style="white-space:pre-wrap">        </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md</a><div><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><span style="white-space:pre-wrap">        </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" 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. When replying, please try to keep the proposal link at the top of the message:<br><br><span style="white-space:pre-wrap">        </span>Proposal link:<br><br><span style="white-space:pre-wrap">                </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md</a><br><br><span style="white-space:pre-wrap">        </span>Reply text<br><br><span style="white-space:pre-wrap">                </span>Other replies<br><br><b>What goes into a review?</b><br><br>The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:<br><br><div><span style="white-space:pre-wrap">        </span>• What is your evaluation of the proposal?<br></div><div><span style="white-space:pre-wrap">        </span>• Is the problem being addressed significant enough to warrant a change to Swift?<br></div><div><span style="white-space:pre-wrap">        </span>• Does this proposal fit well with the feel and direction of Swift?<br></div><div><span style="white-space:pre-wrap">        </span>• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br></div><div><span style="white-space:pre-wrap">        </span>• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></div><div><br></div>More information about the Swift evolution process is available at<br><br><a href="https://github.com/apple/swift-evolution/blob/master/process.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a><br><br>Thank you,<br><br>-Joe<br>Review Manager</div></div></blockquote><br><br>-- <br>-- Howard.<br>