Types after names — Build the smallest useful slice

PART I

Warm-up

Reconnect with a useful idea before starting types after names. 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

Build a typed decision helper

Choose a result type from the question the caller asks. “How many slots remain?” requests an integer. “Is any slot available?” requests a Boolean. Clear result contracts prevent a caller from having to guess whether a numeric value represents data or a decision.

available(capacity,used) returns used < capacity. At (8,3), compare 3 < 8 to obtain true. At (8,8), compare 8 < 8 to obtain false. This helper answers only availability; it does not return the number of free slots or reserve a slot.

Returning capacity - used would answer a different question and produce an integer rather than the declared bool. Do not rely on implicit truthiness of 5 or 0; this exercise uses an explicit Boolean comparison.

Worked reasoning and supplied artifact

fnc available(capacity: i32, used: i32) -> bool {
    return used < capacity;
}

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 available(capacity: i32, used: i32) -> bool {
Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return used < capacity;
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 the available and full cases, then write a separate sentence giving the integer free count for each without changing the helper’s result.

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 types after names.

Create a helper that answers whether a score has passed a threshold using score > threshold. State that equality is not enough under this specific rule, and give below/equal/above cases.

What to produce

A bool-returning helper and three paper cases such as (9,10) false, (10,10) false, (11,10) true.

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 rhythm-game audio editor, demonstrate types after names. Create the smallest .ws integration that demonstrates the section contract. 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 does returning capacity - used not satisfy the shown result contract?It is an integer calculation rather than a Boolean comparisonIt changes the parameter namesEvery subtraction requires a host service

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.

Build a typed decision helper
Choose a result type from the question the caller asks. “How many slots remain?” requests an integer. “Is any slot available?” requests a Boolean. Clear result contracts prevent a caller from having to guess whether a numeric value represents data or a decision.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Write two distinct helper names for free count and availability.

Your recap

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