> On Apr 11, 2016, at 12:30 PM, Dave Abrahams via swift-evolution > <[email protected]> wrote: > > > on Mon Apr 11 2016, Haravikk <[email protected]> wrote: > >> I like the idea in theory, but the question is; is it really safer to return >> a >> result that the developer may not have wanted, versus an error indicating >> that a >> mistake may have been made? > > That's exactly the question. We've considered doing it both ways.
Right. There is a natural tension here between: 1) “fail fast” - so that an error is easily detected and reasoned about by the programmer, and 2) "blunder on” - hope that an error didn’t matter in practice, at the cost to making actual errors harder to diagnose. -Chris _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
