ale/ale_linters/haskell/stack_build.vim

" Author: Jake Zimmerman <jake@zimmerman.io>
" Description: Like stack-ghc, but for entire projects
"
" Note: Ideally, this would *only* typecheck. Right now, it also does codegen.
" See <https://github.com/commercialhaskell/stack/issues/977>.

call ale#Set('haskell_stack_build_options', '--fast')

function ale_linters#haskell#stack_build#GetCommand(buffer) abort
    let l:flags = ale#Var(a:buffer, 'haskell_stack_build_options')

    return 'stack build ' . l:flags
endfunction

call ale#linter#Define('haskell', {
\   'name': 'stack-build',
\   'output_stream': 'stderr',
\   'executable': 'stack',
\   'command_callback': 'ale_linters#haskell#stack_build#GetCommand',
\   'lint_file': 1,
\   '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 21:39:33 +00:00			`" Author: Jake Zimmerman <jake@zimmerman.io>`
			`" Description: Like stack-ghc, but for entire projects`
			`"`
			`" Note: Ideally, this would only typecheck. Right now, it also does codegen.`
			`" See <https://github.com/commercialhaskell/stack/issues/977>.`

Prefer --fast for stack-build (#754) * Vim scripts shouldn't have hyphens Especially not ones that will be autoloaded. You can't have a hyphen in a function name, so autoloading functions based on filename will fail. * Add g:haskell_stack_build_options, default: --fast If we're going to use the --fast option, we may as well go the whole 9 yards and let the user configure the 'stack build' flags. * Create documentation for stack-build options 2017-07-11 12:05:13 +00:00			`call ale#Set('haskell_stack_build_options', '--fast')`

			`function ale_linters#haskell#stack_build#GetCommand(buffer) abort`
			`let l:flags = ale#Var(a:buffer, 'haskell_stack_build_options')`

			`return 'stack build ' . l:flags`
			`endfunction`

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 21:39:33 +00:00			`call ale#linter#Define('haskell', {`
			`\ 'name': 'stack-build',`
			`\ 'output_stream': 'stderr',`
			`\ 'executable': 'stack',`
Prefer --fast for stack-build (#754) * Vim scripts shouldn't have hyphens Especially not ones that will be autoloaded. You can't have a hyphen in a function name, so autoloading functions based on filename will fail. * Add g:haskell_stack_build_options, default: --fast If we're going to use the --fast option, we may as well go the whole 9 yards and let the user configure the 'stack build' flags. * Create documentation for stack-build options 2017-07-11 12:05:13 +00:00			`\ 'command_callback': 'ale_linters#haskell#stack_build#GetCommand',`
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 21:39:33 +00:00			`\ 'lint_file': 1,`
			`\ 'callback': 'ale#handlers#haskell#HandleGHCFormat',`
			`\})`