todo alternatives and similar packages
Based on the "Debug" category.
Alternatively, view todo alternatives based on common mentions on social networks and blogs.
hood8.5 0.0 todo VS hoodHood debugger, based on the idea of observing functions and structures as they are evaluated.
Hoed8.0 0.0 todo VS HoedHoed - A Lightweight Haskell Tracer and Debugger
vacuum7.7 0.0 todo VS vacuumGraph representation of the GHC heap
simple-reflect7.4 0.0 todo VS simple-reflectSimple reflection of expressions
linux-perf6.8 0.0 todo VS linux-perfHaskell library for reading perf.data files from the linux performance events tool.
print-debugger6.2 0.0 todo VS print-debuggerPrints lines with IDE friendly stack traces in Haskell.
htrace5.2 0.0 todo VS htraceHierarchical tracing for debugging lazy evaluation in Haskell
ap-reflect4.9 0.0 todo VS ap-reflectPartial evaluation reflection a la simple-reflect.
remote-debugger4.6 0.0 L4 todo VS remote-debuggerInterface to ghci debugger
debug-trace-var3.7 0.0 todo VS debug-trace-varYou do not have to write variable names twice in Debug.Trace
bytedump3.7 0.0 todo VS bytedumphaskell configurable dump byte helpers
asn1dump3.4 0.0 todo VS asn1dumpASN.1 debug tool
heapsize3.1 0.0 todo VS heapsizeghc-datasize is a tool to determine the size of Haskell data structures in GHC's memory
show-please1.5 0.0 todo VS show-pleaseImproved Show instances for exception and other types
Static code analysis for 29 languages.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of todo or a related project?
Todo wraps some standard debug symbols in warnings so that you'll have to work a bit harder to miss unfinished code in your Haskell programs.
Say that you have this line of code:
neatFunction = undefined
undefined is a good stubbing tool but what if you forget what you were stubbing? You'd like to have some more info on what you were doing, so you do this:
neatFunction = error "Got to implement this someday or my boss will get mad"
This may work but there's some issues with it:
erroris often used for non-total functions, this may confuse the reader
- If we forget to implement the call for
neatFunction, we're not getting noticed that our function currently is incomplete!
Debug.Todo you can do this:
import Debug.Todo neatFunction = todo "I'm going to implement this!"
This will not only solve the cultural ambiguity of
will also throw a compile time warning so if you're using
Wall in your build step, you will get a warning whenever
you forget a
todo in your code!
$ runhaskell example.hs example.hs:5:16: warning: [-Wdeprecations] In the use of ‘todo’ (imported from Debug.Todo): "TODO:s exists in code! Make sure you fix them! "