Skip to content

Conversation

jhrcek
Copy link

@jhrcek jhrcek commented Aug 26, 2022

There's an alarming amount of ghc warnings that clutter build (and CI) output.
I consider it important to strive for warning-free codebase, because even though the warnings are inconsequential, they make it difficult to spot other, potentially more important warnings.

An example of one warning that this fixes:

compiler/src/Parse/Type.hs:46:13: warning: [-Wunused-do-bind]
Warning:     A do-notation statement discarded a result of type ‘[Src.Comment]’
    Suppress this warning by saying
      ‘_ <- Space.chompAndCheckIndent
              E.TParenthesisSpace E.TParenthesisIndentOpen’
   |
46 |             Space.chompAndCheckIndent E.TParenthesisSpace E.TParenthesisIndentOpen

@avh4
Copy link
Contributor

avh4 commented Aug 26, 2022 via email

@robinheghan
Copy link
Member

Yes. That these warnings are intentional should have been communicated better, it's a shame you've wasted time on this @jhrcek .

Closing this issue.

@jhrcek
Copy link
Author

jhrcek commented Aug 27, 2022

True, I should have asked before opening a PR. But don't worry, I didn't waste much time on this. It was like 5 mins of find & replace 😄

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.

3 participants