runtime features / purity checking

✓ 9 passing ○ 1 planned

Lessons

1 ✓ Passing
007 event purity from impure impl
2 ✓ Passing
008 pure proc annotation
3 ✓ Passing
009 unannotated proc impure
4 ○ Planned
011 opaque procs — The point of an [opaque] proc is to have to highlight it as opaque because you're intentionally calling Koru-events FROM a Koru-event, breaking the flow. This has performance implications, and is almost ALWAYS mechanically refactoringable to returning to the calling flow, making the code easier to optimize.
Has docs5 ✓ Passing
012 subflow locally pure
6 ✓ Passing
013 pure on event redundant
7 ✓ Passing
014 subflow transitive pure
8 ✓ Passing
015 event purity from pure impl
9 ✓ Passing
016 subflow impure
10 ✓ Passing
017 module pure proc transitive