[swift-evolution] [Review] SE-0070: Make Optional Requirements Objective-C only
jgroff at apple.com
Mon Apr 25 14:37:47 CDT 2016
I support the approach of making optional requirements ObjC-only. As a nitpick, it feels "wrong" to me to keep a decl modifier around for something that's only a compatibility feature and not natively supported. The proposal notes that a 'objcoptional' modifier was considered and rejected, but why not a single attribute, '@objcOptional' or something like that?
> On Apr 25, 2016, at 10:19 AM, Chris Lattner via swift-evolution <swift-evolution at swift.org> wrote:
> Hello Swift community,
> The review of "SE-0070: Make Optional Requirements Objective-C only" begins now and runs through May 2. The proposal is available here:
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> 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
> Thank you,
> -Chris Lattner
> Review Manager
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution