WillowScript (.ws) is a proposed, not-yet-implemented language. Examples and library integrations here are illustrative design exercises, not verified runnable programs.

Define an event lifetime boundary

A task can outlive the screen or action that started it. Write down who owns that work and which result is still relevant before discussing syntax. Cooperative task scheduling and native background work have different responsibilities and must not be treated as identical.

1. 1

   Define an event lifetime boundary — Discover and trace

   Make a prediction before touching the example.

   Open practice
   →
2. 2

   Define an event lifetime boundary — Build the smallest useful slice

   Change one useful behavior while keeping the contract small.

   Open practice
   →
3. 3

   Define an event lifetime boundary — Change one requirement

   Translate one new mod requirement into a deliberate change.

   Open practice
   →
4. 4

   Define an event lifetime boundary — Boundary detective

   Find a case the simplest success path does not cover.

   Open practice
   →
5. 5

   Define an event lifetime boundary — Flash-check repair

   Use a plausible mistake to show that you understand the mechanism.

   Open practice
   →
6. 6

   Define an event lifetime boundary — Connect the previous skills

   Connect this idea with a previously learned responsibility.

   Open practice
   →
7. 7

   Define an event lifetime boundary — Review and demonstrate

   Collect a useful learning record without pretending the code was executed.

   Open practice
   →