From 15ac7fd8dcc8106eedb370b3d6d0261bb28ed111 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 13 Sep 2026 02:25:07 +0200 Subject: [PATCH] =?UTF-8?q?The=20base=20has=20no=20circularity=20=E2=80=94?= =?UTF-8?q?=20the=20builder=20does=20not=20stand=20on=20it?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Written as an open question; it has an answer, and leaving it open would have made the fix look harder than it is. --- .../00-report.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/04-ISSUES/044-the-runtime-every-module-builds-on-cannot-be-built-by-the-mesh/00-report.md b/04-ISSUES/044-the-runtime-every-module-builds-on-cannot-be-built-by-the-mesh/00-report.md index a70aa91..d4d773b 100644 --- a/04-ISSUES/044-the-runtime-every-module-builds-on-cannot-be-built-by-the-mesh/00-report.md +++ b/04-ISSUES/044-the-runtime-every-module-builds-on-cannot-be-built-by-the-mesh/00-report.md @@ -67,5 +67,7 @@ the mesh can produce it too, because that is all the mesh does. - Is the base a module like any other, or is it one of the few things a new mesh must arrive carrying? It behaves like both: everything is built on top of it, and it is built out of the same sources as everything else. -- If it becomes an ordinary module, what stops the circularity — the base is built by the builder, - and the builder is built on the base? +- If it becomes an ordinary module, is there a circularity? **No** — checked rather than assumed: + the builder is a compiled program built from its own sources and a language toolchain, and does + not stand on this base at all. Only modules written in the mesh's scripted toolchain do. So the + thing that would build the base is not one of the things built on it, and the chain has an end.