Use validated handles instead of raw pointers — Flash-check repair

PART I

Warm-up

Reconnect with a useful idea before starting use validated handles instead of raw pointers. 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

Repair a stale callback update

For a W developer moving into proposed WS, native addresses and native visibility cannot substitute for script-host contracts. Use source-backed exposure concepts and validated-resource boundaries. Exact handle representation, permission workflow and lifecycle APIs remain host requirements rather than invented language methods.

Supplied bridge fixture: A button callback captures H; the view closes; callback later requests navigation using the old context.

The callback’s text reference does not preserve the native owner. Validate lifecycle and authorized navigation context at delivery/use; a late event cannot assume the current screen belongs to it. Exact cancellation methods remain unresolved and must not be fabricated.

Record the request, intermediate decisions and final artifact separately. These are paper derivations and platform-contract exercises; .ws and its native services are not implemented or executed by this school. Shared fnc/domain/import vocabulary does not certify parser support for proposed extensions or prove runtime security enforcement.

Worked reasoning and supplied artifact

// PAPER FIXTURE — Repair a stale callback update
// Manual worked artifact; comments below are not executable source.
// INPUT / CONTRACT: Supplied bridge fixture: A button callback captures H; the view closes; callback later
// requests navigation using the old context.
// DERIVATION / EXPECTED ARTIFACT: The callback’s text reference does not preserve the native owner.
// Validate lifecycle and authorized navigation context at delivery/use; a late event cannot assume the
// current screen belongs to it. Exact cancellation methods remain unresolved and must not be fabricated.

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

Guided exercise: reproduce this exact fixture, annotate each native-versus-script responsibility, then explain why the rejected answer “Yes; captured handles never expire” fails.

• 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: Restricted automation extension. Build a small, understandable change around use validated handles instead of raw pointers.

Create close/late-event/new-view fixtures with allowed and rejected effects. Supply different fixture identities/values from the worked case, a complete predicted result or allow/deny artifact, a stepwise trace, one contrasting failure and the required host contract.

What to produce

Create close/late-event/new-view fixtures with allowed and rejected effects. Preserve source/implementation status and separate manual predictions from future toolchain 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.

import wuix.widget;
const button = widget.Button({
    text: "Continue",
    events: {
        click: fnc() -> void {
            navigator.open("dashboard");
        }
    }
});

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.

• Repair a stale callback update
• A button callback captures H; the view closes; callback later requests navigation using the old context.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Change one field,resource scope,lifetime or input value in the bridge fixture. State the new intermediate decisions and final result without assuming a running WS host.

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