claim
active
claim:every-type-class-morphism-failure-is-an-abstraction-leakEvery type class morphism failure is an abstraction leak.
Source paper
extracted_from(2015) · Elliott, Conal
Neighborhood — ranked by edge-count
Communities (3)
community
- Cross-scale frameworks linking spatial patterns, diagrams, and simplicity as expressions of care in design.
- Applies functional programming principles to UI structure via precise mathematical models, enabling formal verification and revealing computational architecture through interface design.
- Type abstraction and modular correctnessmembers_ofExplores how type systems enforce abstraction boundaries to prevent leaks that compromise modularity and formal guarantees in code.
Related by similarity (8)
cosine ≥ 0.65 · no typed edgeEntities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.
- Consequence of violating the TCM principle.
- Failure of semantic type class morphism; indicates design flaw where type behavior violates its semantic meaning.
- Principle that the instance's meaning follows the meaning's instance; every TCM failure indicates an abstraction leak.
- Another key property.
- Fundamental design principle driving Oberon: proper abstraction enables modular structure and maintainability.
- Claim that algebraic laws are automatically satisfied.
- The instance's meaning follows the meaning's instance (semantic type class morphism principle).claim0.728The core design principle of TCM.