search

Idorobots / spartan

A small Lisp dialect that serves me as a test bed for programming language features.
MIT License
13 stars 3 forks source link

Call trace information in exceptions #92

Open Idorobots opened 3 years ago

Idorobots commented 3 years ago

It would really ease up debugging if the current continuation also contained a call trace up to that point - each &apply invocation should extend it with the closure metadata, while each scope exitting continuation automatically removes the topmost value.

Idorobots commented 3 years ago

A faster solution is to keep a ring buffer of recent call frames in memory - &apply then just pushes a frame into the call trace and then executes it.