Values, expressions, and arithmetic — Connect the previous skills

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

Connect expression evaluation with function calls

An argument can itself be an expression. Reduce that expression to its value before binding the parameter in the called helper. This preserves a clear distinction between the caller’s local calculation and the callee’s contract.

main calls add(3 * 4, 2 + 5). The first argument reduces to 12 and the second to 7, so add receives a = 12 and b = 7. Its own expression a + b returns 19. The helper need not know that 12 came from multiplication or that 7 came from another sum.

Do not substitute operator text blindly into the helper and lose grouping. The parameter a represents the entire first argument value. When you rewrite a trace as one expression, retain the argument boundaries: (3 * 4) + (2 + 5).

Worked reasoning and supplied artifact

fnc add(a: i32, b: i32) -> i32 {
    return a + b;
}
fnc main() -> i32 {
    return add(3 * 4, 2 + 5);
}

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 main() -> i32 {
Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return add(3 * 4, 2 + 5);
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 add(2 * 6, 1 + 3), separating caller reductions from callee binding and return.

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.

Combine a delivery subtotal of 4 parcels at 25 points each with a bonus of 3 plus 7 points. Use add with expressions as arguments and create a trace with separate caller and callee rows.

What to produce

main containing add(4 * 25, 3 + 7), argument values 100/10, and returned prediction 110.

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 values, expressions, and arithmetic. 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 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.

What value is bound to a in add(3 * 4, 2 + 5)?123The literal text 3 * 4

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.

Connect expression evaluation with function calls
An argument can itself be an expression. Reduce that expression to its value before binding the parameter in the called helper. This preserves a clear distinction between the caller’s local calculation and the callee’s contract.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Name one change the caller can make without changing add’s definition.

Your recap

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