does it make sense to have an ast explorer so it's easier to analyze incorrect parsing and canonicalization ? it can be based on https://github.com/fkling/astexplorer
I'm not sure how often it might be needed and if it worth to implement smth like right now
@Joshua Warner made a debugging gui for the parser, I don't know where the code is for that though
It's pretty old, and the code to actually record a trace was never merged
I would like to return to this at some point
The viewer is here: https://github.com/joshuawarner32/debug_buf_viewer
... and the trace recorder is sitting in some old branch / closed PR on the roc repo
Nice. I think this could be written in roc as a TUI using basic-cli and roc-ansi. That would be really cool. :sunglasses:
Yeah, exactly what I was thinking of!
Dug out that old PR -- I think it's this one https://github.com/roc-lang/roc/pull/2213
I remember you have a video too which was super cool to see at the time
Last updated: Jul 06 2025 at 12:14 UTC