Loment 0.1.4

Loment 0.1.4

📢 Notice — Loment 0.1.4 Windows installer

We have identified the following: on some Windows systems, double-clicking loment-0.1.4-windows-x64-setup.exe produces no response whatsoever — no installer window, no error message; the process exits silently with code 0.

The cause has been located. The self-extracting package invokes the installer script by a filename without a path (cmd.exe /c install.cmd), while the script resides in the extraction directory. On systems where the Windows hardening setting NoDefaultCurrentDirectoryInExePath is enabled, cmd no longer searches the current directory and therefore cannot find the script. Note that the same file behaves differently across machines: systems without that setting install normally.

All Windows users are advised to install from the zip archive: unpack loment-0.1.4-windows-x64.zip and run install.cmd in the unpacked directory. Both routes install identical contents.

The fix is complete and will ship with the next release (#114). The published 0.1.4 installer will not be rebuilt — rebuilding would change the bytes published under an existing version number. See #117 for details.

A systems programming language that compiles to native x86-64 — Linux ELF, Windows PE, or a
freestanding object for bare metal — with no runtime and no libc. The toolchain is
self-hosted at run time: compiling and running needs no Python, no clang, no WSL.

Install

Platform	File	How
Linux / WSL	loment-0.1.4-linux-x64.tar.gz	unpack → sh install.sh
Windows	loment-0.1.4-windows-x64.zip	unpack → run install.cmd (or powershell -File install.ps1)
Windows	loment-0.1.4-windows-x64-setup.exe	⚠️ do not use — see the note above
any agent	loment-skill.zip	the language guide on its own, for agents

SHA256SUMS covers the three archives and the skill zip; the installers check it first. Both
install routes put down the same thing: the bootstrap artifacts, the launcher, and the seed.
The Windows installer is unsigned, so SmartScreen will warn once.

Built from main at 0826ac5 (2026-09-23) — share/loment/version inside the package
says so, and that is what the tag v0.1.4 points at.

Verified before publishing: SHA256SUMS checks out for all four files; the Windows zip
installs and the installed toolchain compiles and runs a program natively on Windows
(no clang, no WSL, no Python); the Linux tarball installs in a POSIX shell and its toolchain
does the same in WSL.

What is in it

• The language: Rust-flavoured surface syntax, capability domains
  (capability / guard / excluded / revocable), a frozen surface for this line
  (docs/158).
• Six more surface syntaxes on top of the base one — C, C++, Java, C#, Go, Python: the
  same program, written in any of them.
• A toolchain written in Loment: loment / loment-cli / lompi, plus driver, lsp,
  fmt, doc, lomelf and the native ELF/PE backends. loment run builds a PE program on
  Windows and runs it natively, no clang in the path.
• A standard library in the package: std (127 modules) + host (7), 137 files.
• Potato formal objects (the cross-line contract) exported by the compiler.
• A generated manual, a
  language guide,
  an editor extension, and
  examples.

What is not in it (read this before relying on it)

0.1.4 is a real release, and it is not a claim that everything on the roadmap closed.
The audited checklist is
docs/202;
this is where it stands:

• Not fully self-hosted yet. The toolchain runs without Python, but the repo still carries
  non-Loment development-time code — the Python criteria are being ported to Loment one at
  a time (docs/189).
  Two classes are deliberately exempt (vendored cross-line counterparts; hand-written
  verification shells that wait on a deliverable), and editors/ stays JS/TS because VS Code
  extensions can only be JS/TS (docs/202 §2.3).
• A hosted layer is not there yet. A choose no_std project that pulls in a hosted library
  is not rejected today — that check is the next piece of work (docs/202 §2.4).
• GC is one-tier. free is accepted but is a placeholder (the bump heap does not reclaim);
  choose gc_auto / gc_manual are not in the language yet (docs/175 §3.4).
• The gate is "no new reds", not "all green". The committed baseline still has reds; four of
  them need a private sibling repository a public runner cannot read, so "everything green"
  is not literally attainable today (CONTRIBUTING.md).
• Self-consistency is not correctness. A large part of the evidence is "the reference
  implementation and the self-hosted one agree byte for byte" — two implementations by the same
  author agreeing does not prove the semantics are right. That ceiling is stated in
  docs/203 §7.3,
  which is also where the independent review of the audit package lives (24 claims: 22 accepted,
  1 rejected, 1 unverifiable on the reviewer's machine).
• Known open items are listed honestly, not hidden: see
  docs/158 §4 (12 of
  them, including two that are "consistently wrong on both sides" and therefore invisible to a
  byte-comparison).

Pointers

• What 0.1.4 means and where it is going: docs/175
• The audited release checklist, item by item: docs/202
• Independent review of the audit package: docs/203
• Freeze surface and its cost: docs/158
• Contributing, including how to read a red gate: CONTRIBUTING.md