This form performs a require into a local definition context. It achieves this
by lifting a #%require form to the top level and introducing the
bindings locally with rename transformers. For many purposes this is the same
as a regular require; however, only bindings for the current phase are
made available, and all names are introduced as syntax bindings even if the
exported identifiers included value bindings.

8.2PLaneT Packages

Produces a symbol corresponding to a planet module path for the current
planet package, possibly with a ‹path› (from the grammar of
planet module specs) into the package. This is similar to
this-package-version and similar tools from
planet/util.

Defines a shortcut name for importing modules from planet package
package. Subsequently, (namemodule) is equivalent to
(planetpackage/module) as a require path. For instance, to import the
text and web modules from this package:

This Scribble form corresponds to defmodule within a planet package.
The displayed module path is a planet module path to the current planet
package, possibly with a ‹path› (from the grammar of planet
module specs) into the package. If the #:use-sources option is
present, each src-path is similarly treated as a path into the current
planet package, while each src is treated normally. Both sets of paths
are concatenated and passed to the normal defmodule.

This Scribble form corresponds to defmodule*/no-declare within a planet
package. The displayed module paths are planet module paths to the
current planet package, possibly with ‹path›s (from the grammar of
planet module specs) into the package. Each src-path is
similarly treated as a path into the current planet package, while each
src is treated normally. Both sets of paths are concatenated and
passed to the normal defmodule*/no-declare.

This function produces a value for the parameter
sandbox-namespace-specs such that new sandbox evaluators start with a
namespace constructed by make-ns and share a set of instances of the
modules referred to by the given paths.