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.

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

Run 'cabal check' along with 'hlint' #12

Merged
merged 2 commits into from
Apr 10, 2018
Merged

Run 'cabal check' along with 'hlint' #12

merged 2 commits into from
Apr 10, 2018

Conversation

frerich
Copy link
Owner

@frerich frerich commented Apr 10, 2018

'cabal check' performs some simple sanity checking of the .cabal file,
let's see what happens if we run it with different GHC versions.

Frerich Raabe added 2 commits April 10, 2018 14:35
'cabal check' performs some simple sanity checking of the .cabal file,
let's see what happens if we run it with different GHC versions.
It appears this is more like what's intended to get nice Haddock
documentation. Alas, I couldn't seem to reproduce the 'Expr' example
100% since passing a custom name for the catamorphism via

  $(makeCata defaultOptions { cataName = "foobar" } ''T)

always makes cabal choke with

  cabal: foo.cabal:1:  unexpected span: "''T"

It appears it's because of the curly braces, much like what was noted
in haskell/cabal#968 (but that ticket got
resolved years ago).
@frerich frerich merged commit 77bf954 into master Apr 10, 2018
@frerich frerich deleted the cabal_check branch April 10, 2018 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant