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

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:20:20 UTC

CMP.15:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsUseful correction
Register first, assume the new intersection existsNeither independent author necessarily supplied the joint case.Identify and obtain the joining body before qualifying the combination.
Fold every child by defaultBinding or control can change how child results contribute.Derive the rule from the constructor and operation meanings.
Recurse through the old private evaluatorA new form works at the root but fails under an old constructor.Route recursive calls through the assembled operation.
Let import order select behaviorDeployment changes can silently change meaning.Reject duplicate keys or make selection explicit.
Treat a successful lookup as correctnessA unique body can return a well-typed wrong result.Use distinguishing semantic cases and a scope-appropriate argument.
Equate unchanged files with unchanged behaviorNew dispatch rules or dependencies can redirect old calls.Compare selection and observations on established uses.
Promise arbitrary future combinations from today’s coverage checkFuture variants and operation dependencies were not included.Qualify the declared set and reassemble when it changes.
Buy openness for an unchanged closed problemThe extra interfaces and support have no receiving benefit.Retain the exhaustive closed construction while it suffices.