hdevtools: Persistent GHC powered background server for FAST haskell development tools
|Versions||0.1.0.2, 0.1.0.3, 0.1.0.4, 0.1.0.5, 0.1.0.6, 0.1.0.7, 0.1.0.8, 0.1.0.9, 0.1.1.9, 0.1.2.0, 0.1.2.1, 0.1.2.2, 0.1.3.0, 0.1.3.1, 0.1.3.2, 0.1.4.0, 0.1.4.1, 0.1.5.0, 0.1.6.0, 0.1.6.1|
|Dependencies||base (==4.*), cmdargs, directory, ghc (>=7.2), ghc‑paths, network, syb, time, unix [details]|
|Copyright||See AUTHORS file|
|Source repo||head: git clone git://github.com/bitc/hdevtools.git|
|Uploaded||by BitConnor at Sat Dec 29 01:10:52 UTC 2012|
|Distributions||Debian:0.1.2.2, LTSHaskell:0.1.6.1, NixOS:0.1.6.1, openSUSE:0.1.6.1|
|Downloads||16509 total (116 in the last 30 days)|
|Rating||2.5 (votes: 4) [estimated by rule of succession]|
|Status||Docs not available [build log]
Successful builds reported [all 7 reports]
Hackage Matrix CI
hdevtools is a backend for text editor plugins, to allow for things such as
syntax and type checking of Haskell code, and retrieving type information, all
directly from within your text editor.
The advantage that
hdevtools has over competitors, is that it runs silently
in a persistent background process, and therefore is able to keeps all of your
Haskell modules and dependent libraries loaded in memory. This way, when you
change only a single source file, only it needs to be reloaded and rechecked,
instead of having to reload everything.
hdevtools very fast for checking syntax and type errors (runs just
as fast as the
:reload command in GHCi).
In fact, syntax and type checking is so fast, that you can safely enable auto checking on every save. Even for huge projects, checking is nearly instant.
Once you start using
hdevtools and you get used to having your errors shown
to you instantly (without having to switch back and forth between GHCi and your
editor), and shown directly on your code, in your editor (without having to
wait forever for GHC to run) you will wonder how you ever lived without it.
In addition to checking Haskell source code for errors,
hdevtools has tools
for getting info about identifiers, and getting type information for snippets
[Skip to Readme]
For package maintainers and hackage trustees