Why use Haskeline's outputStrLn vs. conventional putStrLn?

240 views Asked by At

My question: Is there any advantage to using Haskeline's outputStrLn over putStrLn for writing to the screen in a terminal program?

Background:

I recently introduced Haskeline into my terminal app in order to leverage the line-editing UI of the getInputLine function. (This required some significant changes to my monad transformer stack.)

I've since noticed that Haskeline comes with outputStr and outputStrLn functions for output. Now that I've gone to the trouble of adopting the library, I'm wondering if I should also prefer these output functions as opposed to the standard putStr and putStrLn. This would require more refactoring given the different monads returned by the functions in question.

0

There are 0 answers