dead-code-detection alternatives and similar packages
Based on the "Development" category.
Alternatively, view dead-code-detection alternatives based on common mentions on social networks and blogs.
-
hadolint
Dockerfile linter, validate inline bash, written in Haskell -
ShellCheck
ShellCheck, a static analysis tool for shell scripts -
fay-base
A proper subset of Haskell that compiles to JavaScript -
criterion
A powerful but simple library for measuring the performance of Haskell code. -
stgi
A user-centric visual STG implementation to help understand GHC/Haskell's execution model. -
retrie
Retrie is a powerful, easy-to-use codemodding tool for Haskell. -
structured-haskell-mode
Structured editing minor mode for Haskell in Emacs -
cabal-install-parsers
Scripts and instructions for using CI services (e.g. Travis CI or Appveyor) with multiple GHC configurations -
haskell-lsp
Haskell library for the Microsoft Language Server Protocol -
inline-c
Write Haskell source files including C code inline. No FFI required. -
gtk2hs-buildtools
GUI library for Haskell based on GTK+ -
inline-java
Haskell/Java interop via inline Java code in Haskell modules. -
gi-atk
Generate Haskell bindings for GObject-Introspection capable libraries -
lambdabot-core
A friendly IRC bot and apprentice coder, written in Haskell. -
fourmolu
A fourk of ormolu that uses four space indentation and allows arbitrary configuration. Don't like it? PRs welcome! -
c2hs
c2hs is a pre-processor for Haskell FFI bindings to C libraries -
scion
OLD, DEPRECATED: Use this instead https://github.com/haskell/haskell-ide-engine -
lambdabot
A friendly IRC bot and apprentice coder, written in Haskell. -
hie-bios
Set up a GHC API session for various Haskell Projects
Build time-series-based applications quickly and at scale.
Do you think we are missing an alternative of dead-code-detection or a related project?
Popular Comparisons
README
status: experimental
dead-code-detection
detects dead code in haskell projects.
This project is still in an early stage. Currently only those language
constructs have been implemented that I have stumbled across in projects I used
it on. If the tool encounters a language construct that it doesn't understand
yet, it will crash. (I think this is the best behavior since ignoring
unimplemented language constructs would easily result in false positives and
false negatives.) If you use dead-code-detection
on any project and it
doesn't work due to a not implemented language construct, please consider
opening an issue on github.
$ dead-code-detection --root Main -isrc
src/Example/Module.hs:42:23: unusedName