On this page:

2.26 Importing Modules Lazily: lazy-require

The bindings documented in this section are provided by the racket/lazy-require library, not racket/base or racket.


(lazy-require [module-path (imported-fun-id ...)] ...)

Defines each imported-fun-id as a function that, when called, dynamically requires the export named imported-fun-id from the module specified by module-path and calls it with the same arguments.

If the enclosing relative phase level is not 0, then module-path is also placed in a submodule (with a use of define-runtime-module-path-index at phase level 0 within the submodule). Introduced submodules have the names lazy-require-n-m, where n is a phase-level number and m is a number.

When the use of a lazily-required function triggers module loading, register-external-module declares a potential compilation dependency (in case the function is used in the process of compiling a module).