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
This seems fairly simple, and I intend to add support for this myself. The easiest way, if not the "correct" one, is to add a dummy backend that pretty-prints the CompileExpr it receives to a file.
The text was updated successfully, but these errors were encountered:
I don't think so; I guess I should've mentioned that my use-case requires the output to be easily parseable in a way that the output of --dumpcases is not, so I can use it as an input for further processing.
I discussed this with @edwinb yesterday, and it seems we may want to standardise a stable s-expression-style text format for this.
evertedsphere
changed the title
Dump pretty-printed CompileExpr to stdout
Add option to dump CompileExpr in a standard, parseable format
Apr 14, 2020
This seems fairly simple, and I intend to add support for this myself. The easiest way, if not the "correct" one, is to add a dummy backend that pretty-prints the CompileExpr it receives to a file.
The text was updated successfully, but these errors were encountered: