Let's not bring bikeshedding the commonly proposed and rejected union spelling into this. Typed throws would be a nice addition, assuming that the core team finds it in scope for phase 2. It seems only logical that any type can be thrown (i.e. conforms to Error) should be permitted to be listed in `throws()`.
On Fri, Feb 17, 2017 at 1:18 PM, Adrian Zubarev via swift-evolution < swift-evolution@swift.org> wrote: > That’s what I thought too. That’s also the case I showed a simple example > how we could solve the giant list with a typealias even if the pipe | > operator would be exclusive for anything that conforms to Error. > > > > -- > Adrian Zubarev > Sent with Airmail > > Am 17. Februar 2017 um 20:16:30, Anton Zhilin (antonyzhi...@gmail.com) > schrieb: > > 2017-02-17 22:12 GMT+03:00 Adrian Zubarev via swift-evolution < > swift-evolution@swift.org>: > > Is the throwing type always a protocol? In your example it is, but is this >> going to be always the case? >> > I thought it was going to be any one subtype of Error, be it a struct, an > enum, or a protocol existential, or Error itself. > > > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution > >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
