Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Stack init and solver finish up and doc update #1674
Provide, working out of the box experience, for
The documentation in the user guide provides more information and workflow examples.
With these fixes stack init experience must now become much better. We should be able to generate a working stack.yaml for most packages without any issues. If a package has working cabal files and cabal can build it but we are not able to generate a stack.yaml out of the box then it should be considered a bug!
referenced this pull request
Jan 27, 2016
I was having two minds when I did this but ultimately just chose this way. If you think about this data type as a test result measure then then this makes more sense. We perhaps would always want to compare this data type in terms of how good the match was rather than comparing it in the literal sense.
I don't mind using a separate function approach too if that looks clearer.
Sorry for letting this languish so long! I've taken a look at the commits, and they look great.
Since I only have a couple comments / tweaks, I'm going to go ahead and merge this and fix them myself.