Types after names — Change one requirement

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

Change the question and then the result contract

When a feature changes from returning a quantity to answering a decision, revise the declared result as well as the body. Keep caller expectations explicit: code expecting a count cannot assume a Boolean is a numeric replacement.

remaining(10,4) returns the integer 6. The revised question “is there space?” can be answered by hasSpace(10,4), returning 4 < 10, which is true. At (10,10), remaining returns 0 while hasSpace returns false. These results describe related facts but are not the same kind of value.

Changing only -> i32 to -> bool while leaving return capacity - used would leave the contract and body inconsistent. Changing the body without updating the result type has the opposite mismatch. Review both sides together, then review callers.

Worked reasoning and supplied artifact

fnc remaining(capacity: i32, used: i32) -> i32 {
    return capacity - used;
}
fnc hasSpace(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 remaining(capacity: i32, used: i32) -> i32 {
Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return capacity - used;
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 hasSpace(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

Make paired result columns for remaining and hasSpace at (10,4) and (10,10), including result types.

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.

A mod previously returned bonus points. Add a separate helper answering whether bonus points are positive rather than replacing the quantity helper silently. Give signatures and paired predictions for 0 and 5 bonus points.

What to produce

Two purpose-specific helpers and a result table distinguishing 0/5 from false/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 strategy simulation analytics tool, demonstrate types after names. Adapt the task to a second host-neutral application context without changing the imported API 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.

Which revision is needed to change a free-count helper into an availability helper?A Boolean expression and a bool result contract, plus caller reviewOnly a new comment above an integer returnAn automatic conversion from every integer

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.

Change the question and then the result contract
When a feature changes from returning a quantity to answering a decision, revise the declared result as well as the body. Keep caller expectations explicit: code expecting a count cannot assume a Boolean is a numeric replacement.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Name a caller expectation that would break if an integer result silently became Boolean.

Your recap

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