Dispatcher Validation
- Q612: What happens when a dispatcher entry and handler have different purity?
- Q613: Can a derived class dispatcher target a private handler in the parent?
- Q614: What happens if a dispatcher handler's parameter type is outside the hierarchy?
- Q615: How does EK9 check dispatcher return type compatibility?
- Q616: What is dispatcher ambiguity and how is it detected?
- Q617: How can trait diamond patterns cause dispatcher ambiguity?
- Q618: How do sealed dispatchers enforce exhaustive handler coverage?
- Q619: What happens with two-parameter dispatchers and type validation?
- Q620: How does dispatcher resolution work across a class hierarchy?
- Q621: What is the complete set of dispatcher compile-time checks?
- Q849: Why can't a dispatcher see a private handler method in a superclass?
- Q858: How do I avoid dispatcher handler ambiguity with multiple traits?
- Q870: How does adding a concrete type handler resolve dispatcher ambiguity?
- Q1236: Create me a dispatcher method for a sealed Shape trait that has Circle, Square and Triangle handlers, demonstrating exhaustive runtime dispatch.
- Q1244: Create me a dispatcher for a deep class hierarchy (Shape -> Polygon -> Quadrilateral -> Square) where the Polygon handler catches Quadrilateral but a more specific Square handler exists.
- Q1245: Create me a two-parameter dispatcher Combiner with handlers for (Circle, Circle) and (Circle, Rectangle), demonstrating that parameter order matters and unmatched combinations fall back to the entry method.
- Q1344: Why does EK9 report E06320 when a dispatcher handler has a different number of parameters from the entry?