PART I
Warm-up
Reconnect with a useful idea before starting names, parameters, and return types. 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
Choose names that preserve information
A name should help the reader distinguish quantities that share a type. a and b can illustrate addition, but quantity, unitPrice and fee make a shop formula easier to audit. Rename consistently: the declaration and every use inside the body must refer to the same intended binding.
The worked total(quantity,unitPrice,fee) uses each name once in quantity * unitPrice + fee. With (2,150,25), subtotal is 300 and total is 325 cents. If quantity is renamed to itemCount, the body must also use itemCount; leaving quantity behind introduces a name-resolution defect rather than a new pricing rule.
Identifiers are case-sensitive. itemCount and itemcount are different names even if the editor highlights them similarly. Syntax coloring is a visual aid and cannot prove that a renamed reference resolves correctly.
Worked reasoning and supplied artifact
fnc total(quantity: i32, unitPrice: i32, fee: i32) -> i32 {
return quantity * unitPrice + fee;
}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 total(quantity: i32, unitPrice: i32, fee: i32) -> i32 {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return quantity * unitPrice + fee;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
Rename quantity to itemCount consistently, then trace (2,150,25) to confirm the intended rule remains 325.
- 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 names, parameters, and return types.
Replace vague names x, y and z in a fee-bearing ticket-total helper with role-based names. Supply a before/after name map and a trace showing unchanged arithmetic.
What to produce
A consistent rename map, the revised helper and one unchanged-result case; flag any case-only typo.
- 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 total(quantity,unitPrice,fee) uses each name once in quantity * unitPrice + fee. With (2,150,25), subtotal is 300 and total is 325 cents. If quantity is renamed to itemCount, the body must also use itemCount; leaving quantity behind introduces a name-resolution defect rather than a new pricing rule.
Identifiers are case-sensitive. itemCount and itemcount are different names even if the editor highlights them similarly. Syntax coloring is a visual aid and cannot prove that a renamed reference resolves correctly.
Original learning-path task and reference
In a strategy simulation analytics tool, demonstrate names, parameters, and return types. Create the smallest .ws integration that demonstrates the section 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.
- Choose names that preserve information
- A name should help the reader distinguish quantities that share a type. a and b can illustrate addition, but quantity, unitPrice and fee make a shop formula easier to audit. Rename consistently: the declaration and every use inside the body must refer to the same intended binding.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Explain why a name map is useful during a consistent rename.
This marks your personal practice record only. It is not a certification or an official workspace assessment.