Store compiler properties in a key-value map instead of repeatedly invoking ghc --info #1520
Merged
Merged
Conversation
Member
|
LGTM for now. I'm always a bit nervous when code uses "a big bag of crap" (i.e. a string to string map), but I cannot think about anything better right now that doesn't require us to rethink how we represent compiler specific info (which is really what we're doing here, as we really on specific strings created by GHC). |
Member
Author
|
Well, |
Member
|
Go ahead and merge. |
23Skidoo
added a commit
that referenced
this pull request
Oct 11, 2013
Store compiler properties in a key-value map instead of repeatedly invoking `ghc --info`
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #1442.