On Mon, 27 Feb 2017 at 8:44 Dave Abrahams via swift-evolution < [email protected]> wrote:
> > on Fri Feb 17 2017, Joe Groff <[email protected]> wrote: > > > Experience in other languages like Rust and Haskell that use > > Result-based error propagation suggests that a single error type is > > adequate, and beneficial in many ways. > > And experience in still others, like C++ and Java, suggests that > using static types to restrict the kind of information a function can > give you when an error occurs may actually be harmful. +1 here. It becomes wrapping over wrapping over wrapping. Try doing a big app in Java (i.e. some kind of layered server) and you'll understand everything. Ones who tried and still want it - well, there are different tastes out there. > > > -- > -Dave > > _______________________________________________ > 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
