+1 from me as well for the same reasons including a strong preference for naming it "Never" to allow using it in other places than just as return type. This would make it easy to turn it into a real bottom type in the future.
-Thorsten > Am 22.06.2016 um 01:12 schrieb David Hart via swift-evolution > <[email protected]>: > > >> * What is your evaluation of the proposal? > > +1. This makes total sense. But I would recommend naming it “Never” for the > same arguments as in the proposal. > >> * Is the problem being addressed significant enough to warrant a change >> to Swift? > > Yes, it simplifies the language by replacing a rarely used attribute by an > elegant solution from the type system. I also love how Never could be used > with typed throws. > >> * Does this proposal fit well with the feel and direction of Swift? > > Yep: simplification and elegance. > >> * If you have used other languages or libraries with a similar feature, >> how do you feel that this proposal compares to those? > > No. > >> * How much effort did you put into your review? A glance, a quick >> reading, or an in-depth study? > > A good read. > >> >> 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 mailing list >> [email protected] >> https://lists.swift.org/mailman/listinfo/swift-evolution > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
