Direction 15: Effects via capabilities, no effect type system

A function is pure unless it takes a capability parameter. The signature is the purity proof. (Robert: matches)

Session 3 note (tension 1: closure capture)

The Koka comparison showed that an anonymous function can capture a capability, so a closure can do I/O its own type does not show. Robert’s answer: in on Bosque’s rule. Anonymous functions are call-arguments only (never bound to a name, stored, or returned) and captures are read-only; named fns capture nothing. So a captured capability cannot outlive the call and the enclosing signature still bounds every effect. Wording of this direction now reads: “the signature is the purity proof, and effects never hide in a value.” → direction 31.