Data Flow Safety
- Q632: How does EK9 ensure variables are used only after they are defined?
- Q633: How does EK9 track variable initialization across control flow branches?
- Q634: Why must I use a guard expression before accessing a returned value?
- Q635: What operations are forbidden inside a pure method?
- Q636: How do I chain multiple guard expressions for safe access?
- Q687: How should Result values be accessed safely using guard expressions?
- Q688: How does EK9 enforce variable initialization order?
- Q692: How does EK9 ensure class fields are properly initialized?
- Q785: Why must variables be declared before use in EK9?
- Q789: Why does EK9 reject unused variables?
- Q795: What is a logical tautology and why does EK9 reject it?
- Q796: Why does EK9 reject comparisons against variables with known constant values?
- Q1240: Write me a pure function categorise that takes an Integer score and returns a String category ('high', 'medium' or 'low'), proving the return variable is initialised on every branch.
- Q1249: Write me a pure function classifyTemperature that takes a Float celsius and returns a String label, declaring the return variable WITHOUT a default and proving the compiler that every branch of the if/else chain initialises it.