"Developer code must ensure that IAsyncDisposable implementations don't take a long time to complete."

Ah yes, the very technical "long time" unit of measurement. God why don't you just go fuck yourself microsoft

git gud.

That way they can freely change the time limit whenever they want. And if your app breaks, it's your app's fault for taking too long now. 🤡

I thought the point of async was being async

https://learn.microsoft.com/en-us/... reads like this is meant to allow for "lengthy" freeing of unmanaged resources used by managed .net code. "long time" is indeed a stupid term here.

But the whole thing stinks anyways. That i would have to explicitly call DisposeAsync instead of the runtime doing it for me when garbage collecting an object implementing IAsyncDisposable is just asking for a memory leak. I wonder, why they did it that way.

@Root This is real world you live in. It ain't a paradise lol.

@ostream Nope. It’s hell.

https://learn.microsoft.com/en-us/...

Can't find the thing you talk about.

https://learn.microsoft.com/en-us/...
Ah found it sorry.

Just means don't do any long running task in there. This usually means MS had one client doing long really long running shit in there.