Fix a crash & add instructions for next time

Author: pavpanchekha

AGENTS.md

@@ -8,6 +8,12 @@
 - Run `racket src/main.rkt report bench/tutorial.fpcore tmp` to test
   that your changes work; this should take about 5-10 seconds and all
   of the tests should pass, getting basically perfect accuracy.
+- After running tests, you should be able to look into `tmp`, and see
+  one directory per benchmark. Each directory has a `graph.html` with
+  more detail on what happened, including tracebacks for crashes.
+- Herbie prints a seed every time it runs; you can pass --seed N after
+  the "report" argument to fix a seed. That should be perfectly
+  reproducible.
 - You can also run the unit tests with `raco test <file>`, when unit
   tests exist. Often they don't.
 

src/core/egg-herbie.rkt

@@ -287,6 +287,11 @@
       [`(Explanation ,body ...) `(Explanation ,@(map (lambda (e) (loop e type)) body))]
       [(list 'Rewrite=> rule expr) (list 'Rewrite=> (get-canon-rule-name rule rule) (loop expr type))]
       [(list 'Rewrite<= rule expr) (list 'Rewrite<= (get-canon-rule-name rule rule) (loop expr type))]
+      [(list op args ...)
+       #:when (string-prefix? (symbol->string op) "sound-")
+       (define op* (string->symbol (substring (symbol->string op) (string-length "sound-"))))
+       (define args* (drop-right args 1))
+       (cons op* (map loop args* (map (const 'real) args*)))]
       [(list op args ...)
        ;; Unfortunately the type parameter doesn't tell us much because mixed exprs exist
        ;; so if we see something like (and a b) we literally don't know which "and" it is