PART I
Warm-up
Reconnect with a useful idea before starting types after names. 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
Connect an integer helper to a Boolean helper
A caller may pass an integer result into a second helper that asks a Boolean question about it. This composition preserves each helper’s small responsibility and makes the point where the result kind changes visible.
remaining(10,4) first returns i32 value 6. positive(6) then compares 6 > 0 and returns bool value true. At (10,10), remaining returns 0 and positive returns false. The intermediate integer and final Boolean should occupy different rows in the trace.
Do not pass the original capacity to positive if the question concerns remaining capacity. positive(10) would return true even when all ten slots are used. Type compatibility does not prove the correct value was routed between helpers.
Worked reasoning and supplied artifact
fnc remaining(capacity: i32, used: i32) -> i32 {
return capacity - used;
}
fnc positive(value: i32) -> bool {
return value > 0;
}
fnc hasRoom() -> bool {
return positive(remaining(10, 4));
}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 remaining(capacity: i32, used: i32) -> i32 {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return capacity - used;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 positive(value: i32) -> bool {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return value > 0;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 hasRoom() -> bool {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return positive(remaining(10, 4));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 the nested call, labelling remaining’s return i32 and positive’s return bool. Repeat with used 10.
- 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: Workshop stock counter. Build a small, understandable change around types after names.
Compose a points-total helper with a helper that checks whether the total is positive. Supply a case where the starting points are positive but the signed adjustment brings the total to zero, exposing a mistakenly routed starting value.
What to produce
A nested-call draft and traces such as start 5 plus adjustment -5 → total 0 → false, versus the wrong route positive(5) → true.
- 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?
remaining(10,4) first returns i32 value 6. positive(6) then compares 6 > 0 and returns bool value true. At (10,10), remaining returns 0 and positive returns false. The intermediate integer and final Boolean should occupy different rows in the trace.
Do not pass the original capacity to positive if the question concerns remaining capacity. positive(10) would return true even when all ten slots are used. Type compatibility does not prove the correct value was routed between helpers.
Original learning-path task and reference
In a community library utility, demonstrate types after names. Integrate this section with the preceding section’s artifact; identify inputs, outputs, and host capabilities. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.
fnc total() -> i32 {
vary count: i32 = 1;
const bonus: i32 = 2;
count += bonus;
return count;
}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.
- Connect an integer helper to a Boolean helper
- A caller may pass an integer result into a second helper that asks a Boolean question about it. This composition preserves each helper’s small responsibility and makes the point where the result kind changes visible.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Circle the expression where an integer result becomes a Boolean result.
This marks your personal practice record only. It is not a certification or an official workspace assessment.