Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • 11
    Wouldn't it be more appropriate if the red track was below the boxes, thus not running through them? Commented Jun 4, 2018 at 9:33
  • 4
    Logically, you are correct. However, each box in this particular diagram represents a monadic bind operation. bind includes (perhaps creates!) the red track. I recommend watching the full presentation. It is interesting and Scott is a great speaker. Commented Jun 4, 2018 at 10:27
  • 7
    I think of exceptions more like a COMEFROM instruction rather than a GOTO, since throw doesn't actually know/say where we'll jump to ;) Commented Jun 4, 2018 at 17:10
  • 3
    There's nothing wrong with mixing conventions if you can establish boundaries, which is what encapsulation is all about. Commented Jun 4, 2018 at 20:17
  • 4
    The entire first section of this answer reads strongly as though you stopped reading the question after the quoted sentence. The question acknowledges that crashing the program is superior to moving on into undefined behavior: they are contrasting run-time crashes not with continued, undefined execution, but rather with compile-time errors that prevent you from even building the program without considering the potential error and dealing with it (which may end up being a crash if there’s nothing else to be done, but it will be a crash because you want it to be, not because you forgot it). Commented Jun 5, 2018 at 16:05