Type Hierarchy Constraints
- Q602: What is a circular type hierarchy and why does EK9 ban it?
- Q603: How does EK9 detect multi-level circular inheritance chains?
- Q604: Do traits, records, and components also check for circular hierarchies?
- Q605: Why can't I use 'this' inside a standalone function?
- Q606: What is method shadowing and how does EK9 prevent it?
- Q607: Must a class with 'allow only' be declared as open?
- Q608: How do sealed classes differ from sealed traits in EK9?
- Q609: Can sealed enforcement work across module boundaries?
- Q610: How do I refactor circular dependencies using composition?
- Q611: What is the full set of type hierarchy checks EK9 performs?
- Q677: How does abstract implementation flow through a three-level hierarchy?
- Q679: How do sealed classes with allow only work in EK9?
- Q680: How does EK9 resolve the diamond problem with trait method conflicts?
- Q697: How does EK9 limit inheritance depth and what happens when exceeded?