Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:40:20 UTC

CMP.15:3 - Forces

ForceWhat must be reconciled
Independent contribution and shared meaningContributors can avoid editing one another’s modules, but someone must understand both sides of each required new intersection.
Openness and coverageA receiving application needs known behavior for its admitted inputs; future contributions can introduce cases outside that promise.
Reuse and recursive reachAn old handler should remain reusable when a new form occurs below it, while recursive calls must reach the assembled implementation.
Early checking and late compositionStatic interfaces can expose missing capabilities before execution; late selection permits further combinations and introduces visibility and loading conditions.
Extension and preservationAdding a body is easy; showing that old calls still select equivalent behavior depends on the dispatch and effect model.
Flexibility and total costGeneric interfaces, joining bodies, diagnostics and deployment can cost more than maintaining a closed set of cases.