Purity Contracts
- Q560: What does 'as pure' mean on a method in EK9?
- Q561: Why must an override of a pure method also be pure?
- Q562: Why can't I add 'as pure' to an override when the parent method isn't pure?
- Q563: How do pure constructors work and why use ':=?' for field assignment?
- Q564: Why must all constructors be pure if any one is pure?
- Q565: How do I write multiple pure constructors with delegation?
- Q566: What can and cannot be called from a pure method?
- Q567: How does purity flow through multi-level inheritance chains?
- Q568: How does purity apply to operators and their overrides?
- Q569: How do traits interact with pure method contracts?
- Q678: How do pure and non-pure methods coexist in an override hierarchy?
- Q690: How do pure function call chains work and what restrictions apply?
- Q790: Why can't I reassign variables in a pure function?
- Q791: Why can't I call a non-pure function from a pure function?