Haskell

65 readers

3 users here now

**The Haskell programming language community.** Daily news and info about all things Haskell related: practical stuff, theory, types, libraries, jobs, patches, releases, events and conferences and more... ### Links - Get Started with Haskell

founded 1 year ago

Haskell's problem with exploding call stacks (www.channable.com)

submitted 7 months ago by [email protected] to c/[email protected]

1 comments fedilink hide all child comments

By default, Haskell does not provide call stacks when errors occur. To get call stacks, one can add the HasCallStack constraint to any function to request it. However, did you know that doing this carelessly can cause memory usage to explode...

top 1 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 7 months ago

Another way to put it is that HasCallStack isn't optimized away by tail call optimization. And Haskell without tail call optimization will have huge stacks.