Why is State.SetAsync not available for State<T> then only State<T>.UpdateAsync and how to re-empty a State for Reset?

[DevTKSS]

Working with AI MCP it seems to be struggling with the task to create a Model aka ViewModel for a CustomControl-like View (inheriting from SKCanvasElement) and I honestly those problems it was facing while creating the Methods to interact with the State and ListState thrown up challenges I am also not able to solve.

So maybe someone has some answers and recommendations for those steps for us, which includes Copilot, which did 5x query the docs MCP resources and did end up with horrible messy/workaround heavy code, which I would like to clean up to a best practice adhering result 😅

1. How to initialize a non-Generic State for a non-nullable IState which doesn't provides the Empty Operator?

Core Problems:

• IState<RecordType> MyState => State.Empty(this) -> State$${\color{red}.Empty(this)}$$ is not available
• to initialize a non-generic State, we explicitly need a Value init here even if the IState<T> -> T is NOT nullable!
• But this makes the State.SetAsync Operator not longer available

Copilot workaround for constant "possible null return" Compiler Warnings in the later UpdateAsync Operators

private static readonly GameResultReport DefaultReport = new(
        Score: 0,
        Distance: 0,
        HitsRemaining: 3,
        GiftsCollected: 0,
        Timestamp: DateTime.UtcNow);

public IState<bool> HasReport => State.Value(this, () => false);

public IState<GameResultReport> Report => State.Value(this, () => DefaultReport);

The Uno.Samples/UI/MVUX Sample MessengerModel uses a static builder in the record itself, which is cleaner maybe, but if we could have a Generic State with Empty Init, its hard to understand, why we can not with a non-generic one...

So I updated to generic State to get rid of a Default value initalization requirement :

public IState<GameResultReport> Report => State<T>.Empty(this);

But this makes the State.SetAsync Operator not longer available as mentioned. seems like we have to "die one of both death's"? 😬

2. How are we meant to "Reset" the State?

    public async ValueTask ResetAsync(int initialHits = 3, CancellationToken ct = default)
    {
        await HasReport.SetAsync(false, ct);
        await Report.UpdateAsync(
            updater: report => (report ?? DefaultReport) with
            {
                Score = 0,
                Distance = 0,
                HitsRemaining = initialHits,
                GiftsCollected = 0,
                Timestamp = DateTime.MinValue,
            },
            ct: ct);

        await CollectedGifts.RemoveAllAsync(match: _ => true, ct: ct);
    }

but nobody seems to have had in mind to allow a re-empty Operator:

❌ Does both not exist!
await Report.Empty(this);
await Report.Clear(this);