Provide call history when an error is thrown about husk-scheme HOT 4 CLOSED

Some ideas from https://news.ycombinator.com/item?id=5376472 -

Off the top of my head I can think of a doubtless unsophisticated way to recover the "stack" in this situation: namely, the same way you recover the "stack" in the factorial example, by using an accumulator hidden in the interpreter. When foo calls bar(), the interpreter passes along, when it makes the tail call, an explicit list of predecessors (in this case ["foo()"]); when bar calls baz(), the invocation of baz receives ["bar()", "foo()"], etc.

Some Schemes (like MIT Scheme) do this with a circular buffer of bounded capacity. Another Scheme interpreter (a little one by Jake Donham) had a switch to turn off TCO to help debugging. Yet another approach is full omniscient debugging (being able to go backward in time).

from husk-scheme.

Also:

Parent wasn't suggesting to keep full stack frames, but something like (file/function name/line number) tuples, that's not the end of the world. By making it a fixed-size list, you can ensure your memory usage won't blow up.

At the end of the day the goal would be to keep a small amount of information to aid debugging without significantly increasing CPU or memory usage by Husk.

from husk-scheme.

Call history has been added to the interpreter. Compiler support is still TBD, and may not be added for awhile.

from husk-scheme.

This has finally been added in 3.19. Will create a separate ticket for compiler support, since there is more to it...

from husk-scheme.