You can now use make run ARGS="-l setup" to compile racket and a little more to ".zo" form. The ".zo" file is written to “compiled/<platform>/<file>_rkt.zo” as platform-specific code, for now.

Issues: loading compiled code is currently slow, and the ".zo" files are incompatible with any change to “core”, “thread”, “io”, or “regexp”

Exciting!

What is the compiled code the output of?

The chez compiler, the expander, the schemify pass?

The Chez Scheme compiler

I was aiming for a best-case scenario in load times, but it’s currently 10 times as slow as Racket

I don’t yet know why

@spall I think you need to rebase before pushing

@samth why?

your PR now has 25 commits in it, and a merge conflict

how will rebasing get rid of those commits?

Okay there are duplicate commits

most of those commits are by @mflatt

yeah probably from when i rebased last week

how can i fix this?

rebase again

@spall You have things in a state that I don’t know how to adjust easily; I’ll merge with the latest, then apply a diff of that with respect to the latest, then take that patch to a clean tree and apply it (attributed to your email address)

@mflatt I’m working on fixing it right now.

Ok!

@mflatt I think I have fixed it

Should only see the commits I actually made now.

btw, @mflatt, you can review the combined commits here: https://github.com/racket/racket7/pull/5/files

even though it’s multiple commits

I did try to squash all the (new) related commits

@spall I added some comments

@samth I added the extra space to make it super obvious that it was an application

I can remove them

@spall The current version looks ok; I’ll squash before pushing to help make sure I understand the changes