Will await Task.Yield() be optimized away?

I am trying to do this on winform and maui framework:

private async void button1_Click(object sender, EventArgs e)
{
    while(true)
    {
        await Task.Yield();
    }
}

My expectation is that the interface will not become unresponsive, but the result is the opposite of what I thought, the interface is unresponsive anymore.

But my friend has no problem on Xamarin for Android, as expected. I suspect that Yield is optimized away.

[Clockwork-Muse]

… it seems unlikely that just adding 2000 elements would be sufficient to lock the UI for a large amount of time, but rather that whatever you’re doing to gather the data is taking a large amount of time. If it’s your UI code, you may need to refactor something - but what you may need to change is better handled in general coding forums. If it’s the UI framework, reporting performance problems is appreciated, but we’d need a repro.

If it is placed in another thread, it will cause an exception.

You’re right about this. See some of the later entries for examples.

• If updating the UI is actually fast, but gathering the data is slow, just awaiting the results should be sufficient.
• If updating the UI is for some reason slow, you’d probably best be served by creating some form of Progress<T> that you can post results (possibly batched) to. This would increase the time it takes to completely all the updates, but should keep it otherwise responsive.

In either case, your next step is figuring out which more specific part of your code is slow, then asking for more targeted advice on someplace like StackOverflow or the C# discord.

Unless you can provide a specific repro for slow UI in general, there isn’t anything actionable on our end.

[buyaa-n]

I don’t think it is runtime/threading issue, consider @Clockwork-Muse’s suggestion.

Transferring to MAUI for more suggestions on how such UI should be loaded