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
Read the type attached to each name
In name: type, the name identifies a binding or parameter and the type describes the expected kind of value. i32 and bool serve different roles. A Boolean comparison can be a result even when its input is an integer.
hasStock takes stock: i32 and returns bool. For stock 3, stock > 0 evaluates true. For stock 0, it evaluates false. The trace therefore changes kinds at the comparison: input integer → Boolean expression → Boolean return. Nothing here converts the stock itself into a new integer.
Do not infer the result type from the parameter type. A helper reading an integer may return a Boolean decision. The expression after return must fit the declared result; naming the function hasStock does not itself enforce that rule.
Worked reasoning and supplied artifact
fnc hasStock(stock: i32) -> bool {
return stock > 0;
}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 hasStock(stock: i32) -> bool {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return stock > 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.
Try the guided change
Annotate the input and output kinds, then trace stocks 3, 0 and -1 through the comparison.
- 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.
Write a helper that reports whether completed checkpoints is greater than zero. Supply two integer inputs and their Boolean predictions. State why returning the count itself would not express the same typed contract.
What to produce
A typed Boolean helper, inputs 0/2 predicting false/true, and an input/output type map.
- 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?
hasStock takes stock: i32 and returns bool. For stock 3, stock > 0 evaluates true. For stock 0, it evaluates false. The trace therefore changes kinds at the comparison: input integer → Boolean expression → Boolean return. Nothing here converts the stock itself into a new integer.
Do not infer the result type from the parameter type. A helper reading an integer may return a Boolean decision. The expression after return must fit the declared result; naming the function hasStock does not itself enforce that rule.
Original learning-path task and reference
In a puzzle-level authoring tool, demonstrate types after names. Read the source-grounded example and predict its observable behavior before making changes. 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.
- Read the type attached to each name
- In name: type, the name identifies a binding or parameter and the type describes the expected kind of value. i32 and bool serve different roles. A Boolean comparison can be a result even when its input is an integer.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Point to the notation that declares the helper’s result kind.
This marks your personal practice record only. It is not a certification or an official workspace assessment.