Add instructions for running tests with Stack about haskell

[killtheliterate]

Seems stack runhaskell leap_test.hs is halfway there, but stack isn't finding the LeapYear module.

[kytrinyx]

Ah, nice! When you figure it out, would you mind helping update the README?

Does the LeapYear module exist already, or did you fetch the exercise and is stack complaining because you still need to create it?

[killtheliterate]

Yeah, definitely. It may be that cabal-install ends up being the most appropriate way, outside of making each excercism problem a stack project.

[bassjacob]

Alternatively, would you be open to a pr with some docs on how to use stack as a global pkg manager with the exercism problems? I'm happy to take a shot at writing it today.

I ran into this earlier and am reasonably confident I have it setup and working without each problem needing to be its own stack project.

[killtheliterate]

I haven't been able to quite get it working. Got as far as stack install HUnit, and then stack exec foo.hs stops throwing errors about missing deps, but can't find the module under test.

It does seem excessive to make each problem a stack proj. As an end user, the only thing I really care about is not finding myself in "cabal hell" while just trying to learn. Looking forward to seeing what you've got working!

[rbasso]

I agree, @killtheliterate. It would be too disruptive to make each problem a stack project.

Right now I was thinking in the possibility of creating a single exercise as a Stack project, to introduce it to people, but some more general changes would be needed to allow that, and I have no idea about what people here would think about it.

To allow a new stack project kind of exercise, the following files would require a complete rewriting:

• .travis.yml
• bin/check-exercises.hs

Maybe it's not worthy to change it if people are not having trouble compiling the sources...

Anyway, if anyone is interested in the subject, I have a repository with my solutions as stack projects and an improvised .travis.yml with cache enabled to run the tests.

[bassjacob]

@rbasso a how to use Stack for a single problem seems like a great starting point. I honestly wasn't even suggesting that far. I was thinking just

• how to install it
• how to install the required packages to your global config
• what and where to name your solution to the problem
• the command to run to test your solution

This approach would mean you don't have to bundle any of the stack specific code since it's essentially just being used as a cabal replacement, right? Is that worth documenting?

[rbasso]

Sorry! I got that wrong!

Never thought of using Stack's global project. I just use cabal sandboxes and standard stack projects here.

Now I'm curious about how you use it and why!

[bassjacob]

Honestly, in this case just because reorganising exercism/haskell to easily use Stack seemed like more of a pain than it was worth, but I don't have cabal-install installed and had Stack.

Aside from that, to allow the use of ghci with installed packages without needing to be in a project?

[rbasso]

Nice. Even without a project it seems better than the Haskell Platform.

$ stack setup
$ stack install HUnit
$ stack ghci
$ stack runghc leap_test

This is how am I supposed to use it?

ps: Worked in Debian (jessie) / Failed in NixOS (unstable) because of reference to /bin/bash.

[bassjacob]

yep, that's exactly what I did. Stable and easy. I'll write up a snippet for the Readme and open a PR later today?

[rbasso]

Sounds nice. FYI, I don't have access to the repository. Sorry for the confusion.

The last merge was from @kytrinyx , 12 days ago.

[kytrinyx]

Hi, sorry. I've been onboarding in a new job, and haven't checked in all week :/ I would be so grateful for a PR on the README!

[bassjacob]

No worries, I'll draft something simple now 👍

[rbasso]

Considering #147 was merged, this issue should be Closed, right?

[bassjacob]

I guess so? @killtheliterate were those instructions close to what you wanted?

[killtheliterate]

@subshad perfect! Thanks so much.