Several proposals will follow this one: allowing multiple error types, removing Error, replacing rethrows, etc. Those topics are more controversial, but fortunately for them, they mostly add on top of the core feature being discussed. So IMO, if a detail can be split into its own proposal, we should just do it and forget about it for a little while.
2017-02-17 23:16 GMT+03:00 Tino Heth <[email protected]>: > 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. > > > Imho we should remove the restriction that you can only throw > Error-conforming types if typed throws are added: > It's a compatibility feature, and if you manually declare what can be > thrown, you should be allowed to break with Objective-C. > > As Error has no requirements at all, it looks like harassment, as its > whole magic is neither visible nor necessary. > >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
