How do you use Control.Applicative to write cleaner Haskell?

后端 未结 3 1232
野趣味
野趣味 2020-12-12 10:49

In a recent answer to a style question, I wrote

main = untilM (isCorrect 42) (read `liftM` getLine)

and

isCorrect num guess         


        
3条回答
  •  南方客
    南方客 (楼主)
    2020-12-12 11:51

    There is a lot to say in answer to your question, however, since you asked, I will offer this "rule of thumb."

    If you are using do-notation and your generated values[1] are not used in the expressions that you are sequencing[2], then that code can transform to an Applicative style. Similarly, if you use one or more of the generated values in an expression that is sequenced, then you must use Monad and Applicative is not strong enough to achieve the same code.

    For example, let us look at the following code:

    do a <- e1
       b <- e2
       c <- e3
       return (f a b c)
    

    We see that in none of the expressions to the right of <- do any of the generated values (a, b, c) appear. Therefore, we can transform it to using Applicative code. Here is one possible transformation:

    f <$> e1 <*> e2 <*> e3
    

    and another:

    liftA3 f e1 e2 e3
    

    On the other hand, take this piece of code for example:

    do a <- e1
       b <- e2 a
       c <- e3
       return (f b c)
    

    This code cannot use Applicative[3] because the generated value a is used later in an expression in the comprehension. This must use Monad to get to its result -- attempt to factor it into Applicative to get a feel for why.

    There are some further interesting and useful details on this subject, however, I just intended to give you this rule of thumb whereby you can skim over a do-comprehension and determine pretty quickly if it can be factored into Applicative style code.

    [1] Those that appear to the left of <-.

    [2] Expressions that appear to the right of <-.

    [3] strictly speaking, parts of it could, by factoring out e2 a.

提交回复
热议问题