Comment on Unison | A friendly, statically-typed, functional programming language from the future · Unison programming language

• robinm@programming.dev ⁨9⁩ ⁨months⁩ ago

  I’m surprised about this statement, I would have said that exceptions are the consequence of an impure operation (that may or may not fail differently every time you call it).

  source

  • steersman2484@sh.itjust.works ⁨9⁩ ⁨months⁩ ago

    I’m currently learning functional languages and have only limited knowledge, but from what I’ve read now you are right. Throwing exceptions is pure, but catching them is impure.

    In this case I guess the printLine function can throw an exception therefore the calling function must be declared with Exception?

    source

    • robinm@programming.dev ⁨9⁩ ⁨months⁩ ago

      I would even have said that both throwing and catching should be pure, just like returning an error value/handling should be pure, but the reason for the throw/returning error itself is impure. Like if you throw and ioerror it’s only after doing the impure io call, and the rest of the error reporting/handling itself can be pure.

      source

      • Pipoca@lemmy.world ⁨9⁩ ⁨months⁩ ago

        Pure functions should be referentially transparent; you should be able to replace them with whatever value they evaluate to without changing the semantics of your code.

        Throwing is referentially impure: what value do you get from calling x => throw new RuntimeException()?

        Instead, functional languages prefer to return a tagged union of the value or the error.

        source
      • steersman2484@sh.itjust.works ⁨9⁩ ⁨months⁩ ago

        Sounds good,

        but would the preferred way be to use a wrapper type, which holds either the data or the error and avoid exceptions completely?

        source