1. 13
  1.  

  2. 2

    This 20,000-word epic is the single best thing I have ever read about error handling. It covers error codes, checked and unchecked exceptions, assertions, contracts, fail-fast, reliability in concurrent systems … admittedly I haven’t finished it yet so there might be even more gold later on. Wow. 12/10

    Further thought: I have generally been against making assertions fatal, on the grounds that it’s rude for some deeply nested function to make the unilateral decision to kill its process. In part that’s because my background is GUI apps, where said process might contain a bunch of content the user has created but not yet saved; and libraries, which don’t ‘own’ the process. But I’ve been gradually changing my mind, and this paper kind of cements the switch.

    1. 3

      But I’ve been gradually changing my mind, and this paper kind of cements the switch.

      Careful here: to make abandonment work, you not only need to let it crash, but to also have a recovery boundary. In Midory, they have processes as lightweight as threads, so it is effectively an OS-level Erlang.

    2. 2

      sigh

      I can’t off the top of my head think of anything I’m so bummed about being abandoned as Midori.

      Stories with similar links:

      1. Midori's The Error Model via pushcx 6 years ago | 19 points | 2 comments