Separate compilation: the linker's step on compiled units (CoreLink,
CoreLinkN) is well-typed and evaluates in lock-step with source-level
link / linkall.
The linker's binary step, as a relation on compiled units: given a provider
ec₁ : A₁ and a functor ec₂ : {l:A} → B with A₁ ∋ l : A, the linked unit is
linkedCore A₁ {l:A} B ec₁ ec₂. The linearized step is closed — it does not
mention the ambient context — so the relation carries none.
- link (A₁ A B : Core.Typ) (l : String) (ec₁ ec₂ : Core.Exp) : Core.RLookup A₁ l A → CoreLink l A₁ A B ec₁ ec₂ (linkedCore A₁ (Core.Typ.rcd l A) B ec₁ ec₂)
Instances For
Separate compilation (binary link). Elaborate the provider and the
functor separately, compose the compiled pieces with the linker's step, and the
result evaluates in lock-step with source-level link.
Separate compilation reuses a sandboxed client elaborated under the empty context with a compatible provider in any ambient context.
Separate compilation, closed — the toolchain's actual case: closed compiled units, empty initial environment.
Separate compilation (n-ary linkall). As above, with a whole import
interface D wired by projection from the once-bound provider.
Multi-import separate compilation reuses a sandboxed client elaborated under the empty context with a compatible provider in any ambient context.
Separate compilation, n-ary, closed.