ale/ale_linters/haskell/stack_ghc.vim

" Author: w0rp <devw0rp@gmail.com>
" Description: ghc for Haskell files, using Stack

call ale#linter#Define('haskell', {
\   'name': 'stack_ghc',
\   'aliases': ['stack-ghc'],
\   'output_stream': 'stderr',
\   'executable': 'stack',
\   'command': 'stack ghc -- -fno-code -v0 %t',
\   'callback': 'ale#handlers#haskell#HandleGHCFormat',
\})
Add new Haskell linter (#742) * Add stack-build linter for Haskell The stack-build linter works better than the other two linters when you're working with an entire Haskell project. It builds the project entirely and reports any errors. The other two Haskell GHC linters only work on single files, which can result in spurious errors (for example, not being able to find imports). * Document all available Haskell linters * Split GHC checkers into separate files 2017-07-09 17:39:33 -04:00			`" Author: w0rp <devw0rp@gmail.com>`
			`" Description: ghc for Haskell files, using Stack`

			`call ale#linter#Define('haskell', {`
#1754 Require snake_case names for linters in the codebase 2018-07-24 05:05:44 -04:00			`\ 'name': 'stack_ghc',`
			`\ 'aliases': ['stack-ghc'],`
Add new Haskell linter (#742) * Add stack-build linter for Haskell The stack-build linter works better than the other two linters when you're working with an entire Haskell project. It builds the project entirely and reports any errors. The other two Haskell GHC linters only work on single files, which can result in spurious errors (for example, not being able to find imports). * Document all available Haskell linters * Split GHC checkers into separate files 2017-07-09 17:39:33 -04:00			`\ 'output_stream': 'stderr',`
			`\ 'executable': 'stack',`
			`\ 'command': 'stack ghc -- -fno-code -v0 %t',`
			`\ 'callback': 'ale#handlers#haskell#HandleGHCFormat',`
			`\})`