[swift-evolution] [Review] SE-0116: Import Objective-C id as Swift Any type

[David Rönnqvist]

>    * What is your evaluation of the proposal?

+1. I find this to be a solid, well reasoned proposal. 

I enjoyed seeing such a detailed Motivation and am looking forward to discussing the Related Proposals and Future Directions mentioned in this one.

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

Yes. Interoperability between Objective-C and Swift remains important and we don't want to be held back from creating the best possible Swift experience.

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

Yes. 

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

I'm not familiar with (haven't used) libraries that bridge across languages without exposing the same types with the same naming and behaviors in both languages.

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

Read the proposal

- David

> On 5 Jul 2016, at 17:45, Chris Lattner via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Hello Swift community,
> 
> The review of "SE-0116: Import Objective-C id as Swift Any type" begins now and runs through July 11. The proposal is available here:
> 
>    https://github.com/apple/swift-evolution/blob/master/proposals/0116-id-as-any.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.
> 
> What goes into a review?
> 
> 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:
> 
>    * 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,
> 
> -Chris Lattner
> Review Manager
> 
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160706/9599caad/attachment.html>