@mflatt I ran racket-test-core/tests/racket/optimize.rktl and the test is failing

(#<procedure:go>) ==> #t optimize.rktl:4897:8: match: syntax error in pattern in: (linkl-bundle t) location...: optimize.rktl:4897:8 context...: do-raise-syntax-error /home/spall/plt/racket-spall/racket/collects/racket/match/gen-match.rkt:55:23: for-loop /home/spall/plt/racket-spall/racket/collects/racket/match/gen-match.rkt:54:11: mk /home/spall/plt/racket-spall/racket/collects/racket/match/gen-match.rkt:45:9: for-loop /home/spall/plt/racket-spall/racket/collects/racket/match/../../syntax/parse/private/parse.rkt:995:13: dots-loop /home/spall/plt/racket-spall/racket/collects/racket/match/gen-match.rkt:23:0: go

I’m not sure if one of my two changes yesterday caused this.

Any idea?

Just to make sure, "/home/spall/plt/racket-spall/" is a linklet build, not a main-branch build?

yes.

It should be

I’m not seeing the error, but I haven’t tried a 100% fresh build, so I can try that

maybe mines not up to date

Just to check, what does /home/spall/plt/racket-spall/racket/bin/raco pkg show compiler-lib say?

Sorry - make that zo-lib instead of compiler-lib

 [none]
User-specific for installation "6.8.1.4":
 Package[*=auto]  Checksum              Source
 zo-lib*          9098b398716b2f22b...  catalog...kgs/zo-lib

Ok, that’s a problem. Maybe this build was set up before the “zo-lib” package was moved back into the Racket repo.

A fresh build should fix the problem, or maybe raco pkg remove -f zo-lib compiler-lib compiler-doc compiler followed by make

(beware that I didn’t try running any of that!)

The output should be more like this: laptop% ~/linklet/racket/bin/raco pkg show zo-lib Installation-wide: Package[*=auto] Checksum Source zo-lib* static-link /Users/mflatt/linklet/pkgs/zo-lib

with static-link instead of catalog

Ah. yesterday when I built this I only tried to install the future-visualizer package, which installed a lot of other dependencies (obviously). The process was killed by the OS before all the setup finished, maybe that is what caused this. I didn’t worry about it at the time because the package installed and I was able to run my code

@mflatt: Is there a way to view the output of the closure compiler that you mentioned?

Say, to provide sample regexps and view the generated code.

@sabauma It’s a “closure compiler” in the sense that it generates closures, which are not so easy to inspect

You could change “compile.rkt” to add backquotes and unquotes

@mflatt is it possible to get chez to produce stack traces?

I successfully compiled the expander (I think) but it errors with “Exception: returned two values to single value return context” with no further information

The expander compiles for me, too, but many things will prevent it from running

Chez provides inspection facilities that will support stack-trace reporting, but I haven’t tried to write it, yet