> On Feb 15, 2017, at 7:07 AM, Matthew Flatt <[email protected]> wrote: > > TL;DR: I expect the main Racket distribution to run on Chez Scheme > instead of the current Racket VM sometime in the next couple of years. >
Yikes! Exciting! > A Racket on Chez won't be compatible with the current Racket VM at the > level of the C API. For that reason and others, I expect the current > Racket VM to stick around for projects that use the C API, that need > to embed Racket, or so on. The goal of rewriting Racket in Racket has > always been to support multiple VMs, so there's no conflict with > keeping the current Racket VM, too. Other VM efforts, like Pycket and > RacketScript, should also benefit. Still, I expect mainline Racket > development to move to Chez as the primary backend. You mention incompatibility at the level of the C API. I read that three or four times before deciding that this isn’t about those writing Racket packages that use FFI to interact with C libraries, but rather those rare packages that want to use Racket’s C API to interact with Racket. Is this correct? John -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/a68a0c3d-7bcb-4497-be54-b04e52fe7581%40mtasv.net. For more options, visit https://groups.google.com/d/optout.
