<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Generally I'm +1 on this, but I do have a concern. It's not made
explicit in the proposal, but I presume that this is meant to only
be available on Darwin, and not Linux or other platforms that don't
have swift using the Objective-C runtime? (Please correct me if I am
mistaken.)<br>
<br>
I ask because of the swift-corelibs-foundation project; Presumably
once that is complete for Swift 3, code that makes use of this type
bridging should be able to be run cross-platform. For example:<br>
<br>
var a = [AnyObject]()<br>
(a as NSArray).addObject(NSObject()) // should this work on all
platforms?<br>
<br>
swift-corelibs-foundation uses its own protocol named
_ObjectTypeBridgeable (defined here:
<a class="moz-txt-link-freetext" href="https://github.com/apple/swift-corelibs-foundation/blob/338f4bf3a89c75a0420b49f5701466e106af02b5/Foundation/NSSwiftRuntime.swift#L205">https://github.com/apple/swift-corelibs-foundation/blob/338f4bf3a89c75a0420b49f5701466e106af02b5/Foundation/NSSwiftRuntime.swift#L205</a>)
to simulate what happens today on Darwin platforms, but there is no
language support for it so API consumers must explicitly call its
bridging methods. It would be great if corelibs-foundation (and any
code designed to work on Linux) could take advantage of this
proposal to provide the language support, and if the proposal as
written is not intended to have an effect on Linux at all, then I
would suggest we modify it so that the resulting implementation is
not tied to Objective-C and Darwin only.<br>
<br>
-Kevin<br>
<br>
<div class="moz-cite-prefix">On 4/4/2016 1:44 PM, Joe Groff via
swift-evolution wrote:<br>
</div>
<blockquote
cite="mid:18F04A96-1E5F-4A5B-A99E-5CC9F3797B5A@apple.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Hello Swift community,<br class="">
<br class="">
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 class="">
<br class="">
<span class="Apple-tab-span" style="white-space:pre"> </span><a
moz-do-not-send="true"
href="https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md"
class=""><a class="moz-txt-link-freetext" href="https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md">https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md</a></a>
<div class=""><br class="">
Reviews are an important part of the Swift evolution process.
All reviews should be sent to the swift-evolution mailing list
at<br class="">
<br class="">
<span class="Apple-tab-span" style="white-space:pre"> </span><a class="moz-txt-link-freetext" href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br
class="">
<br class="">
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 class="">
<br class="">
<span class="Apple-tab-span" style="white-space:pre"> </span>Proposal
link:<br class="">
<br class="">
<span class="Apple-tab-span" style="white-space:pre"> </span><a class="moz-txt-link-freetext" href="https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md">https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md</a><br
class="">
<br class="">
<span class="Apple-tab-span" style="white-space:pre"> </span>Reply
text<br class="">
<br class="">
<span class="Apple-tab-span" style="white-space:pre"> </span>Other
replies<br class="">
<br class="">
<b class="">What goes into a review?</b><br class="">
<br class="">
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 class="">
<br class="">
<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>•
What is your evaluation of the proposal?<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>•
Is the problem being addressed significant enough to warrant a
change to Swift?<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>•
Does this proposal fit well with the feel and direction of
Swift?<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>•
If you have used other languages or libraries with a similar
feature, how do you feel that this proposal compares to those?<br
class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>•
How much effort did you put into your review? A glance, a
quick reading, or an in-depth study?<br class="">
</div>
<div class=""><br class="">
</div>
More information about the Swift evolution process is available
at<br class="">
<br class="">
<a class="moz-txt-link-freetext" href="https://github.com/apple/swift-evolution/blob/master/process.md">https://github.com/apple/swift-evolution/blob/master/process.md</a><br
class="">
<br class="">
Thank you,<br class="">
<br class="">
-Joe<br class="">
Review Manager</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
swift-evolution mailing list
<a class="moz-txt-link-abbreviated" href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>
<a class="moz-txt-link-freetext" href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a>
</pre>
</blockquote>
<br>
</body>
</html>