You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to basically print racket trace compatible traces and create consumers of these traces as a middle ground between visual debuggers and printf debugging.
Do you like this idea? Would you be open to merging this type of printer upstream if I implement it?
The text was updated successfully, but these errors were encountered:
Hi, I wonder if we should extend the format_enter and format_exit (and prefix_enter/prefix_exit) arguments instead of making a printer just for this trace format:
If we were to make the format customization arguments flexible enough, then others might benefit from it in the future with their own customizations. And you could introduce a wrapper macro (i.e. #[racket_trace]) that wrapped the #[trace] macro with these arguments customized for your trace format.
I think I would be fine merging a PR like that, but my time is very limited and I don't remember how this code works at all so the review might take some time 😅 But if there is a clear example and the tests pass, then I might just merge it with a light review.
Hi! I had a very similar idea, of which I had already created a prototype when I realized your crate already exists.
https://alperenkeles.com/posts/debuggers-for-free/
The idea is to basically print racket trace compatible traces and create consumers of these traces as a middle ground between visual debuggers and printf debugging.
Do you like this idea? Would you be open to merging this type of printer upstream if I implement it?
The text was updated successfully, but these errors were encountered: