You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there Matt,
I'll help out with some of the more gnarly runtime topics of the guide.
I think we can have a guide about "coming from dispatch" and surprising behaviors etc.
One thing I wanted to note down for me to get back to is:
I completely agree this is an important to cover, and I'm really excited about this. I struggled tremendously at first with these exact kinds of things.
However, just a data point. I never used made use of qos in my own code. I had problems with just plain-only Task {} as I transitioned from sync -> async. I think that SE-0431 may help a lot here, especially in the simpler cases.
Hi there Matt,
I'll help out with some of the more gnarly runtime topics of the guide.
I think we can have a guide about "coming from dispatch" and surprising behaviors etc.
One thing I wanted to note down for me to get back to is:
People write this code:
and the equivalent with main actor:
So
Task {} Task{}
cannot be blindly assumed to be FIFO in face of priority escalation, without knowing the exact target actor's executor.We need to properly document what users may expect and what not.
I'll write a portion to the guide about this.
The text was updated successfully, but these errors were encountered: