htrace
debug-trace-var
Our great sponsors
htrace | debug-trace-var | |
---|---|---|
- | 1 | |
9 | 3 | |
- | - | |
0.0 | 0.0 | |
over 10 years ago | almost 6 years ago | |
Haskell | Haskell | |
BSD 3-clause "New" or "Revised" License | MIT License |
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.
htrace
We haven't tracked posts mentioning htrace yet.
Tracking mentions began in Dec 2020.
debug-trace-var
-
I think Zig is hard but worth it
> 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?
bytedump - haskell configurable dump byte helpers
print-debugger - Prints lines with IDE friendly stack traces in Haskell.
Hoed - Hoed - A Lightweight Haskell Tracer and Debugger
ap-reflect - Partial evaluation reflection a la simple-reflect.
vacuum
hood - Hood debugger, based on the idea of observing functions and structures as they are evaluated.
asn1dump - ASN.1 debug tool