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.

Sign up for GitHub

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

Jump to bottom

stack ghci: Ability to specify stanzas of cabal file for different packages #727

Closed
chrisdone opened this issue Aug 6, 2015 · 5 comments
Closed

stack ghci: Ability to specify stanzas of cabal file for different packages #727

chrisdone opened this issue Aug 6, 2015 · 5 comments
Assignees
@chrisdone
Labels
blocked type: enhancement
Milestone
P2: Should

Comments

@chrisdone
Copy link
Member

We can specify like:

$ stack ghci 
$ stack ghci packagename1 packagename2
$ stack ghci packagename1:targetname packagename2
@chrisdone chrisdone self-assigned this Aug 6, 2015
@chrisdone chrisdone mentioned this issue Aug 6, 2015
Closed
@mgsloan
Copy link
Contributor

mgsloan commented Aug 6, 2015

This would be nice! stack ghci currently doesn't work on ide-backend because the test-suite stanza has monads-tf whereas the libraries stanza has mtl. This causes ambiguities for some modules.

@chrisdone chrisdone mentioned this issue Aug 7, 2015
Closed
@borsboom borsboom added this to the 0.3.0.0 milestone Aug 10, 2015
@UnkindPartition
Copy link
Contributor

I need this badly, esp. because some of my test suites are flag-incompatible with their libraries (eg. wrt. NoImplicitPrelude).

@chrisdone
Copy link
Member Author

This is implemented now actually. Try stack ghci packagename:lib packagename:exe:foo or whatnot.

@UnkindPartition
Copy link
Contributor

Ha, indeed! So why is this issue marked as open?

@chrisdone
Copy link
Member Author

Oversight, it came for free as part of another issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chrisdone chrisdone

Labels
blocked type: enhancement
Projects
None yet
Milestone
P2: Should
Development

No branches or pull requests
4 participants
@chrisdone @mgsloan @UnkindPartition @borsboom