[swift-evolution] [swift-evolution-announce] [Review] SE-0102: Remove @noreturn attribute and introduce an empty NoReturn type

[Xiaodi Wu]

+1 from me on the proposal. I'd prefer `Never` for the reasons given above.
"returns Never" reads unambiguously and its reusability elsewhere down the
road (throws Never, etc.) suggests that this might be the most optimal name.


On Thu, Jun 23, 2016 at 1:34 PM, David Sweeris via swift-evolution <
swift-evolution at swift.org> wrote:

> -1 for all the reasons already mentioned.
> Although, if we end up accepting this anyway, FWIW I'd prefer
> "DoesNotReturn" or "NeverReturns" over "NoReturn" or "Never". They both
> read better to me, and their imperative names help make it clearer that
> something is different.
>
> - Dave Sweeris
>
> > On Jun 21, 2016, at 12:03, Chris Lattner <clattner at apple.com> wrote:
> >
> > Hello Swift community,
> >
> > The review of "SE-0102: Remove @noreturn attribute and introduce an
> empty NoReturn type" begins now and runs through June 27. The proposal is
> available here:
> >
> >
> https://github.com/apple/swift-evolution/blob/master/proposals/0102-noreturn-bottom-type.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-announce mailing list
> > swift-evolution-announce at swift.org
> > https://lists.swift.org/mailman/listinfo/swift-evolution-announce
> _______________________________________________
> 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/20160623/d4e16d5c/attachment.html>