PART II
Instruction & guided example
Choose storage from a byte budget
A disposable report preview is 30 MB. At most four previews may be active. The exercise host provides a 100 MB memory budget and an SSD option.
Four previews require 4*30=120 MB before overhead, exceeding the 100 MB bound by 20 MB. Memory-only cannot promise all four. A disk or hybrid policy may fit the feature, but latency, crash persistence and host permissions still need a contract. The proposed tmp storage field is a policy request, not a guarantee of capacity.
Use the supplied case as a paper design exercise. WillowScript and these library integrations are proposed and unimplemented here; no interpreter or native host has checked the example. Preserve the source API spellings, label new policies as exercise-host contracts, and distinguish a predicted result from measured execution.
Worked reasoning and supplied artifact
// PAPER FIXTURE — Choose storage from a byte budget
// Manual worked artifact; comments below are not executable source.
// INPUT / CONTRACT: A disposable report preview is 30 MB. At most four previews may be active. The exercise
// host provides a 100 MB memory budget and an SSD option.
// DERIVATION / EXPECTED ARTIFACT: Four previews require 4*30=120 MB before overhead, exceeding the 100 MB
// bound by 20 MB. Memory-only cannot promise all four. A disk or hybrid policy may fit the feature, but
// latency, crash persistence and host permissions still need a contract. The proposed tmp storage field is
// a policy request, not a guarantee of 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
// PAPER FIXTURE — Choose storage from a byte budgetThis comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// Manual worked artifact; comments below are not executable source.This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// INPUT / CONTRACT: A disposable report preview is 30 MB. At most four previews may be active. The exerciseThis comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// host provides a 100 MB memory budget and an SSD option.This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// DERIVATION / EXPECTED ARTIFACT: Four previews require 4*30=120 MB before overhead, exceeding the 100 MBThis comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// bound by 20 MB. Memory-only cannot promise all four. A disk or hybrid policy may fit the feature, butThis comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// latency, crash persistence and host permissions still need a contract. The proposed tmp storage field isThis comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// a policy request, not a guarantee of capacity.This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
Try the guided change
Reconstruct the supplied worked case first: list its inputs, intermediate decisions and final artifact. Compare each row with the explanation and identify exactly where the rejected alternative fails. Then use the changed inputs in Part IV for independent work.
- 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: Bounded report cache. Build a small, understandable change around choose memory, disk, or hybrid placement.
Budget six 18 MB previews under the same memory limit. Recommend reject, spill or reduce-concurrency behavior and identify retained active work.
What to produce
Budget six 18 MB previews under the same memory limit. Recommend reject, spill or reduce-concurrency behavior and identify retained active work.
- 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.
Need a hint?
Temporary lifetime does not remove a capacity bound. Start by writing the distinct intermediate states or arithmetic before changing the source.
Yes; preview data is temporary is the tempting incorrect conclusion in this case. Temporary lifetime does not remove a capacity bound.
Original learning-path task and reference
In a racing checkpoint editor, demonstrate choose memory, disk, or hybrid placement. Read the source-grounded example and predict its observable behavior before making changes. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.
import tmp;
const cache = tmp.create({
name: "report-cache",
storage: "ssd",
maxSize: "2GB",
lifetime: { duration: "30m", refreshOnAccess: true },
cleanup: { automatic: true, onCrashRecovery: true }
});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.
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.
- Choose storage from a byte budget
- A disposable report preview is 30 MB. At most four previews may be active. The exercise host provides a 100 MB memory budget and an SSD option.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Explain why “Yes; preview data is temporary” fails for the supplied case, then give one changed input that would require revisiting your conclusion.
This marks your personal practice record only. It is not a certification or an official workspace assessment.
