On Thu, Jan 10, 2019 at 10:49 AM Jesper Louis Andersen < jesper.louis.ander...@gmail.com> wrote:
> On Thu, Jan 10, 2019 at 7:39 PM Thomas Bushnell, BSG <tbushn...@google.com> > wrote: > >> >>> The server crashes - that's how we handle "any other exception", as a >> rule. >> >> > I write Erlang for a living. We don't crash a server, ever, on a failure. > Unless the failure is persistent :) > Sorry, Eric was talking about Go, not just "something". There may be other choices that would solve the problem where Go would not. I think the paper you linked is exciting, and actually suggests that the hard work which needs to be done will solve the problem without a change of language. This fits my intuition: the things necessary to take advantage of type safety can only be automatically used with the same kind of proof work you need to do to establish the code was fine to begin with. Thomas -- memegen delenda est -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
