[swift-evolution] Review: Import Objective-C Constants as Swift Types

[Jeff Kelley]

Hi John,

	What’s the status of this review?


Jeff Kelley

SlaunchaMan at gmail.com | @SlaunchaMan <https://twitter.com/SlaunchaMan> | jeffkelley.org <http://jeffkelley.org/>
> On Feb 18, 2016, at 6:41 PM, John McCall via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Hello, Swift Community.
> 
> The review of the proposal "Import Objective-C Constants as Swift Types" begins now and runs through February 23rd, or this coming Tuesday.
> 
> The proposal is available here:
> 
>   https://github.com/apple/swift-evolution/blob/master/proposals/0033-import-objc-constants.md <https://github.com/apple/swift-evolution/blob/master/proposals/0033-import-objc-constants.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 (me). When replying, please try to consistently top-post, keeping the proposal link at the top of the message, like so:
> 
>   Proposal link:
>     https://github.com/apple/swift-evolution/blob/master/proposals/0033-import-objc-constants.md <https://github.com/apple/swift-evolution/blob/master/proposals/0033-import-objc-constants.md>
> 
>   This proposal is perfect.  I can no longer imagine programming in Swift without this proposal in place.
> 
>   Alice wrote on 3 Ventôse:
>   > This proposal is completely in keeping with revolutionary principles.
> 
> Uniformity here makes my life easier, so thank you in advance.
> 
> 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 here:
> 
>   https://github.com/apple/swift-evolution/blob/master/process.md <https://github.com/apple/swift-evolution/blob/master/process.md>
> 
> Thanks!
> 
> John McCall
> 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/20160307/c03b5da8/attachment.html>