>>2
Right, just as >>3 said, since the premise here is using the same core in multiple engines, obviously it has to be portable across all Scheme dialects that end up used in such engines. Of course, they're hypothetical right now, but we could at least start out writing code targeting a smaller Scheme standard and let the host engine developers argue about whether to support extra features.