Fix benchmark compilation on stack #135
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
44 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorry to keep bombarding you with pull requests of this nature, but I didn't realize during #134 that
stackis stricter thancabal-installabout listing things inother-modules. Whereascabal-installonly cares if it can find the modules it needs somewhere inhs-source-dirs(i.e., ifcabal sdisthappens to grab them somehow),stackexplicitly requires every dependent module to be listed in another-modulesstanza...Anyway, the fix is once again simple, one just has to cram more stuff into
unordered-containers.cabal.