Mutable and stable bindings — Review and demonstrate

PART I

Warm-up

Reconnect with a useful idea before starting mutable and stable bindings. 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.

Recall note

A rough note is enough. You can revise it after the example.

PART II

Instruction & guided example

Review binding choices with a mutation ledger

A mutation ledger lists each binding, its initial value, every later write and its final value. It is a practical way to justify vary and const choices. The ledger also makes accidental extra updates visible before any real execution is available.

In the worked helper, stock starts 5, delivery stays 3, and stock receives two writes: after += delivery it is 8; after += 2 it is 10. The ledger records stock: 5 → 8 → 10, delivery: 3 throughout. The final return reads 10, not the earlier 8.

Do not stop a trace at the first successful-looking value. Return observes state at its own location in the path. If the requirement promised only one delivery, the extra += 2 is a semantic defect even though stock is correctly declared mutable.

Worked reasoning and supplied artifact

fnc stockAfterUpdates() -> i32 {
    vary stock: i32 = 5;
    const delivery: i32 = 3;
    stock += delivery;
    stock += 2;
    return stock;
}

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 stockAfterUpdates() -> 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 = 5;
Introduce a binding intended to change. Identify its initial value now so later updates can be traced rather than guessed.
const delivery: i32 = 3;
Name a value that this example keeps stable. Inspect the right-hand side for the value or configuration being bound.
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 += 2;
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.

Try the guided change

Build the full ledger and circle the value read at return. Explain the purpose of each update.

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.

Prediction or guided notes

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.

Your drafts remain here. Continue whenever you are ready.

PART IV

Independent practice

Project context: Workshop stock counter. Build a small, understandable change around mutable and stable bindings.

Review a counter starting at 14 that receives a stable delivery of 5 and then a correction of -2. Include all writes, justify the binding keywords and state whether a second application of the delivery would violate the intended operation.

What to produce

Ledger 14 → 19 → 17, stable delivery 5, and a duplicate-delivery counterexample ending at 22.

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.

Your .ws practice draft

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?

Original learning-path task and reference

In a community library utility, demonstrate mutable and stable bindings. Submit source, acceptance cases, and an explanation proving the section objective. 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.

Which stock value does the worked return read?10 after both updates8 immediately after the first update5 from the declaration regardless of writes

Explain a normal or boundary case

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.

Review binding choices with a mutation ledger
A mutation ledger lists each binding, its initial value, every later write and its final value. It is a practical way to justify vary and const choices. The ledger also makes accidental extra updates visible before any real execution is available.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Write the ledger entry that would reveal a duplicated delivery update.

Your recap

This marks your personal practice record only. It is not a certification or an official workspace assessment.