[swift-evolution] [Review] SE-0160: Limiting @objc inference

[David Beck]

* What is your evaluation of the proposal?
In theory, it seems like a great idea, but I fear that it will be one of
those small changes that have disastrous effects on migrating code to Swift
4. There will likely be a ton of confusing errors and warnings that amount
to "just add @objc to everything". Where there won't be errors or warnings,
I can imagine that behavior could change in ways that most people can't
predict.

* Is the problem being addressed significant enough to warrant a change to
Swift?
A 5% reduction in binary size is significant, and an issue that Swift is
certainly running into. However I suspect that there are other ways to
address this.

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

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

* How much effort did you put into your review? A glance, a quick reading,
or an in-depth study?
Read through the proposal.

On Tue, Mar 21, 2017 at 11:03 PM, Chris Lattner via swift-evolution <
swift-evolution at swift.org> wrote:

> Hello Swift community,
>
> The review of "SE-0160: Limiting @objc inference" begins now and runs
> through March 28. The proposal is available here:
>
>         https://github.com/apple/swift-evolution/blob/master/
> proposals/0160-objc-inference.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, 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
>
> Thanks!
>
> -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/20170322/c53f506a/attachment.html>