Mutable and stable bindings — Connect the previous skills

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 returned calculation as stable input to an update

A stable local binding can hold a calculated result. Stability concerns whether that binding is reassigned, not whether the right-hand side is a literal. This lets a helper separate “calculate the delivery” from “apply the delivery.”

add(3,4) returns 7. const delivery receives 7 and keeps that value. stock starts at 10, then stock += delivery changes stock to 17. The trace crosses a helper boundary and then a state transition: inputs 3/4 → returned 7 → stable delivery 7 → updated stock 17.

The helper does not re-run add every time delivery is read in the shown trace; delivery names the returned value. Do not label delivery mutable merely because add performed arithmetic. Only stock receives a later update here.

Worked reasoning and supplied artifact

fnc add(a: i32, b: i32) -> i32 {
    return a + b;
}
fnc received() -> i32 {
    vary stock: i32 = 10;
    const delivery: i32 = add(3, 4);
    stock += delivery;
    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 add(a: i32, b: i32) -> i32 {
Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return a + b;
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 received() -> 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 = 10;
Introduce a binding intended to change. Identify its initial value now so later updates can be traced rather than guessed.
const delivery: i32 = add(3, 4);
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.
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

Write the add return as its own row before creating the delivery binding. Follow it into stock’s 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.

Start with 20 supplies, combine two delivery packs of 6 and 9 using a helper, and apply that returned amount once. Identify the mutable and stable bindings and their final values.

What to produce

A composed draft with delivery 15, stock 35 and separate call/return and before/after rows.

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 media review console, demonstrate mutable and stable bindings. Integrate this section with the preceding section’s artifact; identify inputs, outputs, and host capabilities. 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.

Why may delivery use const even though its initializer calls add?The binding is not reassigned after receiving the resultFunction results can never be integersconst prevents the helper from calculating

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 returned calculation as stable input to an update
A stable local binding can hold a calculated result. Stability concerns whether that binding is reassigned, not whether the right-hand side is a literal. This lets a helper separate “calculate the delivery” from “apply the delivery.”
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Name the moment when the delivery value first becomes available.

Your recap

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