Does Racket have a way to address the need to, say, create a dispatching table during syntax expansion and read from that table at runtime? I don't know Racket well, but I've been able to do similar things easily in Guile, Common Lisp, and Clojure without an issue. Googling this problem leads me to believe that it can't be done, which is a pretty severe handicap to have if you're a Lisp.
Also adding that what I was doing in Guile, Common Lisp, and Clojure was sloppy. After searching for the case macro, saying 'aha!', and applying what I learned into creating an equivalent Racket macro, I realize that it was a portable solution to Guile, and the same idea applies for non-hygienic macro systems.
(If the example is not too long, perhaps you can paste it here.)
0: http://synthcode.com/scheme/chibi/lib/chibi/scribble.html
R7RS small maintains this same mentality. R7RS big is basically R7RS small with a large standard library.
The problem people have been trying to work through is that many people like a small, clean, minimalist core Scheme, but many other people (well, some are the same people, myself included) don't think the current standard is enough to produce useful interoperability. Especially implementors like being able to write small self-hosted experimental or embedded Schemes without a large standard. But many people writing Scheme code are not all that happy about the poor interoperability story that ends up resulting, because there is not quite enough standardized to write libraries that will work on all the major schemes, which is why there's no Scheme equivalent of CL's Quicklisp repository of cross-implementation libraries (the SFRI system is the only real attempt to make this sort-of happen, and is not really good enough).
For R7RS-large, are there plans for a module standard?
And yet, R7RS-large _still_ will not have a standardized FFI.
0: http://en.cppreference.com/w/cpp/language/language_linkage
1: https://www.haskell.org/onlinereport/haskell2010/haskellch8....
2: https://docs.oracle.com/javase/8/docs/technotes/guides/jni/
3: https://common-lisp.net/project/cffi/
4: https://en.wikipedia.org/wiki/Foreign_function_interface#Exa...
This solution is hugely superior to having none at all; as it means that bindings to foreign libraries may trivially be ported across many Schemes. Choosing the right Scheme will be less about what libraries are available, and more about which provides the best execution environment for your needs.
In this case, doing the right thing happens to be doing nothing more than warning the user, as is often the case. Attempting to design a system that safely captures foreign state with continuations is almost certainly an over-engineered solution.
1. kitchen sink
2. extract core
3. redefine kitchen sink as `small` + extras
R5RS: [0]
R6RS: [1]
R7RS: [2] (Page 22)
And many Schemes provide non-standard extensions; for instance, Chicken supports non-hygienic macros[3].
FWIW, I prefer to think of the two stages as "syntax expansion" and "evaluation", and not "compile time" and "run time". Compilation and running are loaded terms that don't appropriately capture the totality of situations where this behaviour applies, in Scheme.
0: http://schemers.org/Documents/Standards/R5RS/HTML/r5rs-Z-H-8...
1: http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-14.html#node_se...
2: http://trac.sacrideo.us/wg/raw-attachment/wiki/WikiStart/r7r...
3: http://wiki.call-cc.org/explicit-renaming-macros