PART I
Warm-up
Reconnect with a useful idea before starting state changes with vary. 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
Build a workshop stock counter with a complete ledger
The workshop project should make the start, each change and the final result understandable to another learner. Use a local mutable stock binding, stable names for supplied adjustments where useful, and an explicit unit of parts. Keep persistence, event subscriptions and concurrent edits outside the claim unless a real host contract is supplied.
The worked workshop begins with 24 parts, receives 8 and applies a correction of -3. Trace stock 24 → 32 → 29. The independent sum 24 + 8 - 3 also gives 29. A no-delivery case (24,0,-3) gives 21, while a no-correction case (24,8,0) gives 32. These isolate the contributions of each update.
A counter with correct arithmetic can still be unsafe in a real workshop if the same delivery event is applied twice or two writers overwrite each other. Record those as future host requirements rather than claiming your local helper solves them. The public completion marker records your practice, not an executed inventory transaction.
Worked reasoning and supplied artifact
fnc workshopStock(initial: i32, delivery: i32, correction: i32) -> i32 {
vary stock: i32 = initial;
stock += delivery;
stock += correction;
return stock;
}
fnc main() -> i32 {
return workshopStock(24, 8, -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 workshopStock(initial: i32, delivery: i32, correction: i32) -> i32 {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
vary stock: i32 = initial;Introduce a binding intended to change. Identify its initial value now so later updates can be traced rather than guessed.
stock += delivery;Read the current value, add the right-hand amount and store the new value. A before/after trace makes the state change visible.
stock += correction;Read the current value, add the right-hand amount and store the new value. A before/after trace makes the state change visible.
return stock;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 workshopStock(24, 8, -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
Rebuild the three worked ledgers and justify why stock uses vary while the inputs describe fixed values for each call.
- 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 state changes with vary.
Create a counter for 30 parts, a delivery of 12 and a correction of -5. Include normal, zero-delivery, zero-correction and excessive-removal cases. Explain whether the feature should permit negative states and name one host guarantee required before real inventory use.
What to produce
A complete source draft; traces predicting 37, 25, 42 and a stated excessive-removal result; units, mutation rationale, policy and host-limit notes.
- 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 workshop begins with 24 parts, receives 8 and applies a correction of -3. Trace stock 24 → 32 → 29. The independent sum 24 + 8 - 3 also gives 29. A no-delivery case (24,0,-3) gives 21, while a no-correction case (24,8,0) gives 32. These isolate the contributions of each update.
A counter with correct arithmetic can still be unsafe in a real workshop if the same delivery event is applied twice or two writers overwrite each other. Record those as future host requirements rather than claiming your local helper solves them. The public completion marker records your practice, not an executed inventory transaction.
Original learning-path task and reference
Integrate every section in this module into Workshop stock counter. Submit .ws source, a list of approved host APIs, eight acceptance cases, and a short explanation. Demonstrate Mutable and stable bindings; Types after names; State changes with vary.
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.
- Build a workshop stock counter with a complete ledger
- The workshop project should make the start, each change and the final result understandable to another learner. Use a local mutable stock binding, stable names for supplied adjustments where useful, and an explicit unit of parts. Keep persistence, event subscriptions and concurrent edits outside the claim unless a real host contract is supplied.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Summarize your stock counter’s input, transition rule, final prediction and most important unimplemented host requirement.
This marks your personal practice record only. It is not a certification or an official workspace assessment.