[swift-evolution] [Review] SE-0057: Importing Objective-C Lightweight Generics
Douglas Gregor
dgregor at apple.com
Fri Apr 1 00:19:12 CDT 2016
> On Mar 31, 2016, at 2:40 PM, Andrew Bennett via swift-evolution <swift-evolution at swift.org> wrote:
>
> A few quick questions:
>
> * Is there a swift-evolution discussion thread? It's marked as TODO currently.
Thanks for catching that. The thread is here:
http://thread.gmane.org/gmane.comp.lang.swift.evolution/2886
and I’ve updated the proposal with a link.
> * What if you want your generic parameter to be a protocol instead of a class?
The generic parameter itself can be required to conform to @objc protocols; the generic argument will be able to be an @objc protocol when the protocol conforms to itself.
- Doug
>
> Thanks!
> Andrew Bennett
>
> On Friday, 1 April 2016, Chris Lattner via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> Hello Swift community,
>
> The review of "Importing Objective-C Lightweight Generics" begins now and runs through April 5. The proposal is available here:
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0057-importing-objc-generics.md <https://github.com/apple/swift-evolution/blob/master/proposals/0057-importing-objc-generics.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 <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, 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 you 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 <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 <javascript:;>
> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> _______________________________________________
> 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/20160331/c43a442d/attachment.html>
More information about the swift-evolution
mailing list