PART I
Warm-up
Reconnect with a useful idea before starting instructions and observable results. In one or two sentences, describe the input, output or host boundary from the previous exercise that this lesson builds on. If you are arriving directly, skim the worked example first; there is no locked prerequisite.
A rough note is enough. You can revise it after the example.
PART II
Instruction & guided example
Change a requirement and trace the whole effect
A requirement describes intended behavior. An implementation is one way of achieving it. Changing the two inputs of an addition does not change the operation itself; introducing a multiplier does. Distinguish a data change from a rule change before editing.
The worked bonus rule is base + bonus * 2. With base 10 and bonus 3, multiplication first gives 6 and addition gives 16. If the requirement instead says “double the entire reward,” the expression must be (base + bonus) * 2: first 13, then 26. The same inputs expose the difference clearly.
Changing the example call to reward(20,6) scales the data but does not explain whether the bonus alone or the whole reward is doubled. A useful trace names intermediate meanings: doubled bonus = 6, total = 16. This prevents an attractive but incorrect edit that changes the business rule.
Worked reasoning and supplied artifact
fnc reward(base: i32, bonus: i32) -> i32 {
return base + bonus * 2;
}
fnc main() -> i32 {
return reward(10, 3);
}Illustrative example from the proposed WillowScript design. The language and WUIX/WMATH/WDB/WAUDIO/WTMP services are not implemented in the supplied source. This site has no interpreter, VM or native host and does not execute or certify the snippet.
Walk through the example, one line at a time
fnc reward(base: i32, bonus: i32) -> i32 {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return base + bonus * 2;Evaluate the following expression using the current values, then send its result to the caller. Explain the value; do not confuse it with printed output.
}Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
fnc main() -> i32 {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return reward(10, 3);Evaluate the following expression using the current values, then send its result to the caller. Explain the value; do not confuse it with printed output.
}Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
Try the guided change
Trace both expressions with base 8 and bonus 2. Keep the two predictions, 12 and 20, labelled by the rule each implements.
- Write the supplied inputs and initial state before following the example.
- Reconstruct each intermediate calculation or host decision, then compare with the worked artifact.
- Explain why the contrasting alternative fails before attempting the changed inputs in Part IV.
PART III
Take a breather
Step back after the guided example. Look away from the screen, stretch, or reread your prediction. This is an optional learning pause, not a timer or an assessment gate.
When you return, try to name the lesson’s key idea without copying its wording. If that feels difficult, return to Part II and trace one line rather than restarting the entire lesson.
PART IV
Independent practice
Project context: Snack-shop calculator. Build a small, understandable change around instructions and observable results.
A level designer changes the rule from “double the bonus” to “double the whole reward.” Edit the helper, preserve its inputs, and show before/after traces for (5,4) and (0,4).
What to produce
A revised helper and a before/after table: (5,4) gives 13 then 18; (0,4) gives 8 in both rules.
- State the intended behavior in a sentence before editing.
- Use only source-backed syntax and the host services whose contract you have been given.
- Record a normal case and a boundary or unavailable-resource case.
- Label hand predictions separately from anything actually measured in a supplied toolchain.
Syntax colors are a reading aid, not a compiler. The line you are editing stays uncolored until you move to a different line; capitalization is never changed. Drafts stay on this browser and code is not executed.
Need a hint?
The worked bonus rule is base + bonus * 2. With base 10 and bonus 3, multiplication first gives 6 and addition gives 16. If the requirement instead says “double the entire reward,” the expression must be (base + bonus) * 2: first 13, then 26. The same inputs expose the difference clearly.
Changing the example call to reward(20,6) scales the data but does not explain whether the bonus alone or the whole reward is doubled. A useful trace names intermediate meanings: doubled bonus = 6, total = 16. This prevents an attractive but incorrect edit that changes the business rule.
Original learning-path task and reference
In a puzzle-level authoring tool, demonstrate instructions and observable results. Adapt the task to a second host-neutral application context without changing the imported API contract. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.
fnc add(a: i32, b: i32) -> i32 {
return a + b;
}
fnc main() -> i32 {
return add(2, 3);
}Where the original task needs a host API that is not supplied here, write the contract and predictions. Do not invent a runtime result.
PART V
Self-check
Use this check to notice what to revisit. It does not award a private course grade, block another page or claim to verify compiled code. Every answer has a learning explanation.
You may keep exploring even if you are unsure. Use the hint, compare the trace, and revise your explanation.
PART VI
Recap & small task
Bring the idea back to the mod feature you are building. A useful recap connects the mechanism to a decision you can make in your own code.
- Change a requirement and trace the whole effect
- A requirement describes intended behavior. An implementation is one way of achieving it. Changing the two inputs of an addition does not change the operation itself; introducing a multiplier does. Distinguish a data change from a rule change before editing.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Explain why the zero-base case alone cannot distinguish these two rules.
This marks your personal practice record only. It is not a certification or an official workspace assessment.