3 ms·
These look like nice tools. In CL land I think we can find some of their functionality in other tools than Slime, such as SLY, a fork of Slime with more feature
by vindarel 4y ago
These look like nice tools. In CL land I think we can find some of their functionality in other tools than Slime, such as SLY, a fork of Slime with more features:
> - Instrument any Clojure form
This would be Stickers: annotate any Lisp form with a sticker, run your code, interactively walk through the recordings.
https://joaotavora.github.io/sly/#Stickers https://joaotavora.github.io/sly/#Stickers
> - Provide a GUI to explore your values and execution flow
SLY has an improved trace dialog: https://joaotavora.github.io/sly/#Trace-Dialog https://joaotavora.github.io/sly/#Trace-Dialog Also LispWorks' visual stepper is easier to use than SLY or Slime's. There is also an in-progress portable visual stepper for CL: https://zenodo.org/record/3742759 https://zenodo.org/record/3742759
> time travel stepper
ah. Nice job.
- jpmonettas 4y agoNice, thanks for the links. Yeah I don't know how stickers trace code, but FlowStorm tracing debugger takes advantage of the immutable data structures used everywhere and by default in Clojure. You can then instrument entire code bases, run them, and tracing is just a matter of retaining(leaking) pointers of every intermediate expression so the GC doesn't collect them. I don't think this is possible when working with mutable objects, since then only way would be to somehow serialize the objects involved at every step so you can analyze the data later, which is prohibitively expensive in most situations.