Values, expressions, and arithmetic — Flash-check repair

PART I

Warm-up

Reconnect with a useful idea before starting values, expressions, and arithmetic. 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

Distinguish a missing term from wrong grouping

Different defects need different repairs. A missing term discards information; wrong grouping applies a valid operation to the wrong quantity. Diagnose the counterexample before changing multiple operators at once.

The promised rule is base + count * each. A broken helper returns count * each, omitting base. With base 7, count 2 and each 3, the promised steps are 2 * 3 = 6 then 7 + 6 = 13; the broken result is 6. Adding the base repairs the missing term. Parenthesizing (base + count) * each instead gives 27, a different defect.

Testing base = 0 would conceal the missing term. A meaningful failing case uses a nonzero base. After repair, keep both zero-base and nonzero-base cases; their purposes differ even if both are useful regression checks.

Worked reasoning and supplied artifact

// Broken: the base reward is missing.
fnc reward(base: i32, count: i32, each: i32) -> i32 {
    return count * each;
}

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

// Broken: the base reward is missing.
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
fnc reward(base: i32, count: i32, each: i32) -> i32 {
Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return count * each;
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

Repair the helper and show why the alternative (base + count) * each still fails (7,2,3).

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: Snack-shop calculator. Build a small, understandable change around values, expressions, and arithmetic.

A shop total omits a 30-cent fixed fee and returns quantity * price. Repair the draft and write cases for 2 items at 80 cents, no items, and a fee of zero. State whether charging a fee on an empty order is a policy question.

What to produce

Corrected expression, arithmetic predictions 190/30/160 under the stated rule, and an empty-order policy 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 classroom scheduling assistant, demonstrate values, expressions, and arithmetic. Explain the flash answer, locate a plausible mistake, and repair the relevant part of your task. 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.

Which input choice reveals an omitted base term?A nonzero baseOnly base zeroOnly count zero and base 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.

Distinguish a missing term from wrong grouping
Different defects need different repairs. A missing term discards information; wrong grouping applies a valid operation to the wrong quantity. Diagnose the counterexample before changing multiple operators at once.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Write the expected result of reward(4,3,2) before evaluating the broken expression.

Your recap

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