Functions as reusable contracts — Review and demonstrate

PART I

Warm-up

Reconnect with a useful idea before starting functions as reusable contracts. 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.

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

PART II

Instruction & guided example

Review portable reasoning and missing execution evidence

The shared fnc/parameter/return grammar can make a Willow learner feel immediately at home, but familiar arithmetic does not establish that a proposed .ws program has a runtime. Treat each helper as a typed input/result contract and keep the caller’s units and role assumptions explicit. This bridge separates portable reasoning from unverified execution.

The sample review packet contains the typed fee helper, input (275,25), hand trace 275+25=300 cents, a zero-fee case, and source-status note: proposed .ws, no supplied interpreter. It lists future evidence separately: actual toolchain acceptance and actual caller observation under a documented host. This is a complete reasoning artifact without pretending to be an execution report.

A .w compiler test cannot automatically certify a different .ws path. Browser-local practice completion also cannot award private grades or prove native output. Preserve the useful arithmetic evidence while accurately stating the missing execution layer.

Worked reasoning and supplied artifact

// Worked contract artifact:
// The sample review packet contains the typed fee helper, input (275,25), hand trace 275+25=300 cents, a zero-fee case, and source-status note: proposed .ws, no supplied interpreter. It lists future evidence separately: actual toolchain acceptance and actual caller observation under a documented host. This is a complete reasoning artifact without pretending to be an execution report.

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.

Try the guided change

Build the sample packet and label each field source fact, hand prediction or future observation.

• 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.

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.

PART IV

Independent practice

Project context: Shared pricing rules. Build a small, understandable change around functions as reusable contracts.

Submit a reusable pricing helper review with two differently priced callers, three expected cases and a short explanation of what carries from Willow knowledge versus what remains unimplemented in WillowScript.

What to produce

Source draft, role/unit contract, independent cases and explicit missing runtime/host evidence.

• 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.

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.

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

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.

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 portable reasoning and missing execution evidence
• Build the sample packet and label each field source fact, hand prediction or future observation.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Build the sample packet and label each field source fact, hand prediction or future observation.

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