todo VS debug-trace-var

Compare todo vs debug-trace-var and see what are their differences.

todo

Wrapping development symbols in Warnings to make sure you don't miss them (by nyson)

debug-trace-var

You do not have to write variable names twice in Debug.Trace (by ncaq)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
todo debug-trace-var
- 1
1 3
- -
0.0 0.0
over 1 year ago almost 6 years ago
Haskell Haskell
BSD 3-clause "New" or "Revised" License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

todo

Posts with mentions or reviews of todo. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning todo yet.
Tracking mentions began in Dec 2020.

debug-trace-var

Posts with mentions or reviews of debug-trace-var. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-01.
  • I think Zig is hard but worth it
    9 projects | news.ycombinator.com | 1 Jun 2023
    > Can you give me an example of a Haskell expression which isn't reverentially transparent (without unsafePerformIO)?

    Yes: https://github.com/ncaq/debug-trace-var The trick, however, is not unsafePerformIO (destructive mutability has nothing to do with referential transparency in general) but with TemplateHaskell, as quoting has everything to do with referential transparency.

    > But the bog standard FP definition is a real and useful concept.

    Actually, it's rather tautological. It defines FP circularly (see my comment here: https://news.ycombinator.com/item?id=36152488). It says nothing more than the far more useful explanation: "the meaning of every expression is a value".

What are some alternatives?

When comparing todo and debug-trace-var you can also consider the following projects:

Hoed - Hoed - A Lightweight Haskell Tracer and Debugger

print-debugger - Prints lines with IDE friendly stack traces in Haskell.

ap-reflect - Partial evaluation reflection a la simple-reflect.

vacuum

htrace - Hierarchical tracing for debugging lazy evaluation in Haskell

hood - Hood debugger, based on the idea of observing functions and structures as they are evaluated.

heapsize - ghc-datasize is a tool to determine the size of Haskell data structures in GHC's memory