Matthew Flatt ad98dc0ddf track import "shapes" as procedure or structure type ... Shape information allows the linker to check the importing module's compile-time expectation against the run-time value of its imports. The JIT, in turn, can rely on that checking to better inline structure-type predicates, etc., and to more directy call JIT-generated code across module boundaries. In addition to checking the "shape" of an import, the import's JITted vs. non-JITted state must be consistent. To prevent shifts in JIT state, the `eval-jit-enabled' parameter is now restricted in its effect to top-level bindings. original commit: d7bf677645		2012-10-30 13:29:28 -06:00
..
commands	raco exe: checks on source and destination paths	2012-05-28 20:30:58 -06:00
demodularizer	bytecode validator: check "constant" annotations on variable references	2012-10-19 11:27:52 -06:00
bundle-dist.rkt	rename all files .ss -> .rkt	2010-04-27 16:50:15 -06:00
decompile.rkt	track import "shapes" as procedure or structure type	2012-10-30 13:29:28 -06:00
embed-sig.rkt	rename all files .ss -> .rkt	2010-04-27 16:50:15 -06:00
sig.rkt	remove obsolete and unused Racket-to-C compiler	2011-09-20 15:26:39 -06:00
zo-marshal.rkt	track import "shapes" as procedure or structure type	2012-10-30 13:29:28 -06:00
zo-parse.rkt	track import "shapes" as procedure or structure type	2012-10-30 13:29:28 -06:00
zo-structs.rkt	track import "shapes" as procedure or structure type	2012-10-30 13:29:28 -06:00