Mutable and stable bindings — Boundary detective

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

Use a zero adjustment to reveal state flow

A zero adjustment should leave a counter’s current value unchanged. That makes it a useful check of the read/add/store model, but it cannot prove that the update used the correct nonzero adjustment. Combine it with at least one revealing transition.

Start with count 8 and delta 0. count += delta reads 8, adds 0 and stores 8. With delta -3, it reads 8 and stores 5. Both inputs are integers. Whether negative changes or negative final counts are permitted belongs to the feature’s policy, not to the existence of vary.

A mistaken assignment count = delta would also end at 0 in an all-zero case, but with starting 8 and delta 0 it discards the starting value. Keep a nonzero starting state to expose replacement-versus-increment mistakes.

Worked reasoning and supplied artifact

fnc adjust(starting: i32, delta: i32) -> i32 {
    vary count: i32 = starting;
    count += delta;
    return count;
}

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 adjust(starting: i32, delta: i32) -> i32 {
Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
vary count: i32 = starting;
Introduce a binding intended to change. Identify its initial value now so later updates can be traced rather than guessed.
count += delta;
Read the current value, add the right-hand amount and store the new value. A before/after trace makes the state change visible.
return count;
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 (8,0) and (8,-3), then contrast += delta with = delta for the zero-delta case.

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.

For a stock adjustment helper, provide no-change, delivery and removal cases starting at 15. Include one removal larger than stock and record the arithmetic result separately from the policy question.

What to produce

A transition matrix such as 15+0=15, 15+4=19, 15-6=9 and 15-20=-5 with an invalid-stock note.

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 strategy simulation analytics tool, demonstrate mutable and stable bindings. Add normal, boundary, and invalid-input cases and explain expected behavior. 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.

Starting at 8, what is the difference between count += 0 and count = 0?The first preserves 8; the second replaces it with 0Both always preserve 8Both automatically reject zero

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.

Use a zero adjustment to reveal state flow
A zero adjustment should leave a counter’s current value unchanged. That makes it a useful check of the read/add/store model, but it cannot prove that the update used the correct nonzero adjustment. Combine it with at least one revealing transition.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Choose one case that would fail if += delta were accidentally replaced by = delta.

Your recap

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