Skip to content

Comments

Add conflictSetOrigin debugging field#3397

Merged
23Skidoo merged 1 commit intohaskell:masterfrom
edsko:pr/conflictSetOrigin
May 4, 2016
Merged

Add conflictSetOrigin debugging field#3397
23Skidoo merged 1 commit intohaskell:masterfrom
edsko:pr/conflictSetOrigin

Conversation

@edsko
Copy link
Contributor

@edsko edsko commented May 4, 2016

This field is only added if the debug-conflict-sets flag is specified to
cabal config; it adds a tree to CallStacks to a ConflictSet. This is very
useful when trying to understand how a certain conflict set was constructed.

/cc @kosmikus

This field is only added if the `debug-conflict-sets` flag is specified to
`cabal config`; it adds a tree to `CallStack`s to a `ConflictSet`. This is very
useful when trying to understand how a certain conflict set was constructed.
@edsko
Copy link
Contributor Author

edsko commented May 4, 2016

Note that this requires GHC 7.10; trying to configure with -f debug-conflict-sets with older GHC will result in a solver failure. (The docs for CallStack claim we need ghc 8.0; I think this is a documentation bug: http://ghc.haskell.org/trac/ghc/ticket/12013 .)

@23Skidoo 23Skidoo merged commit 688542b into haskell:master May 4, 2016
@23Skidoo
Copy link
Member

23Skidoo commented May 4, 2016

Merged, thanks!

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants