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
Right now we dump the DOT format but that's unreadable. It'd be cool to use something like https://dot-to-ascii.ggerganov.com/ and save the ASCII format.
Using perl seems fine but we'd have to make sure the installation is super easy and automatic and works everywhere. We could also setup a webserver do it or hand-code something similar (e.g., maybe not a "true" rendering but just extracting the foo --my--> bar edges or something).
The text was updated successfully, but these errors were encountered:
@lqd, I'm responding to this comment on this thread:
ASCII output would be super cool, but maybe svg or another image format would be easier and acceptable in the meantime ? It's not really easily readable as text, but neither is a sufficiently large/complicated .dot file. We can easily do svg output in pure rust via https://github.com/nadavrot/layout.
I think what we really want is the ability to specify the "interesting bits" of the heap-graph dump in the #? annotation.
Right now we dump the DOT format but that's unreadable. It'd be cool to use something like https://dot-to-ascii.ggerganov.com/ and save the ASCII format.
Relevant research into how this can be done
Using perl seems fine but we'd have to make sure the installation is super easy and automatic and works everywhere. We could also setup a webserver do it or hand-code something similar (e.g., maybe not a "true" rendering but just extracting the
foo --my--> bar
edges or something).The text was updated successfully, but these errors were encountered: