Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

parse cabal file for doctest params #84

Open
alanz opened this issue May 17, 2014 · 3 comments
Open

parse cabal file for doctest params #84

alanz opened this issue May 17, 2014 · 3 comments

Comments

@alanz
Copy link
Collaborator

alanz commented May 17, 2014

I have put together a generic doctest driver based on the library in a cabal file, see
https://github.com/alanz/HaRe/blob/wip/test/doctests.hs

This introduces a dependency on ghc-mod.

I am not sure if I should make a pull request here, or if it should live in a different place

@sol
Copy link
Owner

sol commented May 20, 2014

Hey! In general this is something we want to have. But having a dependency on ghc-mod is somewhat problematic. Maybe put it into a separate package (e.g. cabal-doctest), so that people can experiment with it. If we see it is more useful than @ekmett's custom Setup.hs, we could then try to get rid of the ghc-mod dependency and eventually ship it with doctest.

@alanz
Copy link
Collaborator Author

alanz commented May 20, 2014

Where can I see @kmett's custome Setup.hs?

On Tue, May 20, 2014 at 6:21 AM, Simon Hengel [email protected]:

Hey! In general this is something we want to have. But having a dependency
on ghc-mod is somewhat problematic. Maybe put it into a separate package
(e.g. cabal-doctest), so that people can experiment with it. If we see it
is more useful than @ekmett https://github.com/ekmett's custom Setup.hs,
we could then try to get rid of the ghc-mod dependency and eventually
ship it with doctest.


Reply to this email directly or view it on GitHubhttps://github.com//issues/84#issuecomment-43585112
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants