[aura-1.4] Prelude ==> BasicPrelude && Formatting ==> th-printf#383
[aura-1.4] Prelude ==> BasicPrelude && Formatting ==> th-printf#383fosskers merged 1 commit intofosskers:aura-1.4from
Conversation
sformats to a more C-printf looking function.|
Shouldn't BasicPrelude be the first import? |
|
I could only see that mattering if doing so rendered other imports redundant. |
|
It's mainly a style thing. The prelude isn't a "normal" import, and is less noise when set apart from the other imports. |
|
I can agree with that. Let's add that to the style guide (which also has to be updated to reflect the removal of the Aura monad). |
|
Right. Just a moment, I'll update the PR. On Wed, Jan 6, 2016 at 3:10 PM, Colin Woodbury notifications@github.com
"Open-source software has fewer bugs because it admits the possibility of |
f2efb36 to
3e5d651
Compare
3e5d651 to
f05e4f6
Compare
|
Re: |
|
@fosskers I guess the package is from here: https://github.com/pikajude/th-printf Looks like |
|
Just took a look. I realize I should probably be using that for everything, haha. Things like: foo name age = "Hello " ++ name ++ ", you are " ++ show age ++ " years old!"are clumsy. I especially like its ability to produce |
[aura-1.4] Prelude ==> BasicPrelude && Formatting ==> th-printf
|
Thanks again @theotherjimmy for this! |
|
@fosskers : lol. The same can be said for python. I guess plenty of language prefer using printf style output in some form for everything. |
|
That shows me there's something inherently good about |
This one is much simpler, just making the switch to basic-prelude and changing all of the
sformats to a more C-printf looking function. The reasoning of the Formatting to th-printf switch is simple: I did not see th-printf earlier, or I would have used it instead of Formatting from the beginning. My bad XD.