putStrLn is missing about rio HOT 3 CLOSED

Could be naked IO is evil. I see there's a logging library in RIO, maybe I'm being encouraged to use that?

This was my assumption when I discovered the absence of all the console output functions. Personally, I'm OK with it; import System.IO is not expensive, and it forces you to actually think when you're reaching for putStrLn. For prototyping it's fine, but there's usually a better long-term solution.

from rio.

Have a look at #5, and also the beware of readFile blog post which deals with questions around character encoding for textual I/O functions. In other words, the reason we haven't added putStrLn yet is because it's unclear what the correct design point is.

For now, I'd recommend either using the built-in logging code, or importing RIO.Text qualified and using those functions.

I'm definitely open to resolving this situation better, input welcome. It may be better though to consolidate the discussion on #5.

from rio.

Got it, thanks @snoyberg, I'll close this ticket so the conversation can continue on #5.

from rio.