lungo builds Lean 4.35.0 projects as well as Lean 4.34.1 ones: a project’s lean-toolchain
may name either release. Anything else is refused before Lake runs, with the supported
releases listed: another release, a release candidate, a nightly or a channel such as
stable. The message says so when the release is newer than lungo.
The installed toolchain must be the release it is named after: its lean --version must
report the release’s commit as well as its number.
Each generated program reports the Lean release it was compiled from (Lean.versionString,
Lean.githash), and programs compiled from different releases work side by side in one
process: the runtime behaves, for each program, as its release’s runtime does where the two
releases differ (ST.Ref reads and writes shared between threads, Nat.pow of zero or one
to an exponent beyond a machine word, a second TCP shutdown, a failed group lookup).
For Lean 4.35.0 programs: Float.fma, Float32.fma and Nat.powMod are provided; arrays,
byte arrays and strings carry Lean’s linearity mark through copies, and with
LEAN_ABORT_ON_NONLINEAR set in the environment a program stops when one marked as linear
has to be copied because it is shared (not under WebAssembly). A path dependency that Lake
copies into the packages directory (copy = true) is read from that copy, as Lake builds it.
Runtime
A signal watcher that fails to start fails again the next time it is asked for a signal,
rather than returning a promise that is never resolved.
Two lungo commands fetching the same runtime archive or wasi-sdk at once no longer remove
each other’s copy: the second waits for the first and uses its copy.
The runtime’s C ABI is version 3 (lungo_abi_v3): programs generated by this lungo need its
runtime.
Updates
When lungo self update refuses to install a release, its message words the reason
differently.