Design 47 H: H-A-157, package edges come from go.mod requirements
This commit is contained in:
@@ -783,3 +783,13 @@ Where two preparers disagreed, the chosen one is named.
|
||||
default 2, carried and read the same way as that one (its file resource under the state dir and its env name in
|
||||
the same form). The builder compares its picture by the step ask's source revision; a step ask with no source (a
|
||||
run on request) does not wait. P11, P7 (the existing form).
|
||||
- **H-A-157 (package edges come from go.mod, never from go.sum or a past build alone, 17:13)** Met before the
|
||||
second proof: at main's revision 21, 64 of 82 Go modules carry no package edge (mesh-delivery-sdk, the gate, the
|
||||
node-engine among them), because the indexer's version line reads the mesh packages go.sum names, and go.sum names
|
||||
none since every mesh package is required at the zero version (ADR 0573 §2); the import form stands only once a
|
||||
trunk build reported imports, which no module built before the clean state has. G §47 makes kind-1 edges from what
|
||||
a module's build source imports: the indexer takes a module's mesh packages from the `require` lines of its go.mod
|
||||
(every mesh package path, at any version, the zero version included), at the take-in, with no build needed; a
|
||||
build's reported imports refine that set once they exist, and never replace it with an empty one while go.mod
|
||||
names a mesh package. The sibling rule (H-A-136) stands. Acceptance test 112 then holds for a module never built
|
||||
since the clean state. P3, P7.
|
||||
|
||||
Reference in New Issue
Block a user