[swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

[Howard Lovatt]

 • What is your evaluation of the proposal?

Good idea, it gets rid of compiler magic

• Is the problem being addressed significant enough to warrant a change to
Swift?

Yes, plenty of mixed projects. Plenty of Cocoa libraries that could be
improved with a Swift API.

• Does this proposal fit well with the feel and direction of Swift?

Yes, obj-c is still important

• If you have used other languages or libraries with a similar feature, how
do you feel that this proposal compares to those?

No, but have wanted this in Swift

• How much effort did you put into your review? A glance, a quick reading,
or an in-depth study?

Followed discussions on swift-evolution


On Tuesday, 5 April 2016, Joe Groff via swift-evolution <
swift-evolution at swift.org> wrote:

> Hello Swift community,
>
> 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:
>
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md
>
> Reviews are an important part of the Swift evolution process. All reviews
> should be sent to the swift-evolution mailing list at
>
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
> 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:
>
> Proposal link:
>
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md
>
> Reply text
>
> Other replies
>
> *What goes into a review?*
>
> 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:
>
> • What is your evaluation of the proposal?
> • Is the problem being addressed significant enough to warrant a change to
> Swift?
> • Does this proposal fit well with the feel and direction of Swift?
> • If you have used other languages or libraries with a similar feature,
> how do you feel that this proposal compares to those?
> • How much effort did you put into your review? A glance, a quick reading,
> or an in-depth study?
>
> More information about the Swift evolution process is available at
>
> https://github.com/apple/swift-evolution/blob/master/process.md
>
> Thank you,
>
> -Joe
> Review Manager
>


-- 
-- Howard.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160405/d70fe063/attachment.html>