-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: Print docstring for instructions executed in trace as part of report #256
Comments
Still learning clojure, but would something like this work for what you need? |
Yes, though I'm not sure how those would work for some of the indirectly-constructed instruction functions, like But I was just thinking of adding a line to the report in each step like this (untested) code
|
It looks like
Meaning it could still be documented the same way:
Definitely agree on moving it from within eval-push to it's own function though (and handling non-instructions as well), will take another stab at it this weekend. |
I often find myself explaining, step by step, what a trace is doing in each step. The constants and input values are straightforward; the instructions can be more complicated.
I'd like to suggest printing the docstring for each instruction as it's executed in a trace, for the reader. Needless to say, if there's some other use (besides being read by a human being) for the trace itself, this could be an option. But it seems like it would be almost universally helpful for any trace, especially for people unfamiliar with the details of complex instructions, like
'exec_do*range
.The text was updated successfully, but these errors were encountered: