Salam Pərviz bəy. Rekursivlik əvəzinə "state machine" məntiqi istifadə olunur. Bu isə sadə bir if..else-dir. Amma bəli, çağrılma mexanizmi rekursiyaya bənzəyir
When movenext function calling. first it calling it if Task.Iscompleted then same thread over the process but if task.iscompleted ==false how it again call movenext?
Hi Kanan, Thank you very much for your message. Great question. Please check 34:11 to see the answer. The simple answer is: There is an if..else condition and "AwaitUnsafeOnCompleted" internally calls MovesNext again by referring to the same instance
it would be great if you could make a video about how to prepare for a C# Interview with the type of coding questions that the interviewers may ask, thanks for your contribution to the comunity! greetings from Madrid, Spain!
I want to add a small clarification. At 39:46, we need to add Task.FromResult in the same line where Task.Delay was, to better understand the difference. (The intention was clear, but in the order shown on the screen, the same thread would be displayed even if Task.Delay were there)
Hey Karan, thank you for being a valuable member of our channel. Of course, we have scheduled another interesting video on C# + Microservices for tomorrow.
I appreciate your hard work, keep it up. Best wishes
Thank you so much! I'm glad my hard work is making a difference.
Great video!
Glad you enjoyed it
Salam Tural bəy, bu prosesi bir növ "async" lə başlayan ilk methodun daxilindekileri recursive olaraq çağırması kimide başa düşmek olar?
Salam Pərviz bəy. Rekursivlik əvəzinə "state machine" məntiqi istifadə olunur. Bu isə sadə bir if..else-dir. Amma bəli, çağrılma mexanizmi rekursiyaya bənzəyir
When movenext function calling. first it calling it if Task.Iscompleted then same thread over the process but if task.iscompleted ==false how it again call movenext?
Hi Kanan, Thank you very much for your message. Great question. Please check 34:11 to see the answer. The simple answer is: There is an if..else condition and "AwaitUnsafeOnCompleted" internally calls MovesNext again by referring to the same instance
Great explanation!
Glad it was helpful!
What a great explanation!
Thank you very much! You may consider my russian language channel (TuralSuleymaniTech RU) which I have launched recently
@@TuralSuleymaniTech Cool! Is it a neuron net translated channel?
Nope, that is actually me speaking in russian and recording everything from scratch
it would be great if you could make a video about how to prepare for a C# Interview with the type of coding questions that the interviewers may ask, thanks for your contribution to the comunity! greetings from Madrid, Spain!
Thank you for the suggestion! I'll definitely consider making a video on preparing for a C# interview with coding questions.
I want to add a small clarification. At 39:46, we need to add Task.FromResult in the same line where Task.Delay was, to better understand the difference. (The intention was clear, but in the order shown on the screen, the same thread would be displayed even if Task.Delay were there)
Hey, thanks for your comment. If the intention is clear, it means, there is no problem
Perfetto, very nice explanation . As you mentioned in title "LIKE A SENIOR"
I appreciate you taking the time to watch and comment, Tarlan. I'm happy you enjoyed it!
really good explanation! 👌keep up with this amazing videos
Your kind words mean a lot! I'm happy I could make the video helpful and interesting.
Keep cooking
Wait, but what about ConfiugreAwait(false)?
hey, we have another tutorial in our channel called "Async UI" that explains ConfigureAwait(false)
Keep Posting,
Hey Karan, thank you for being a valuable member of our channel. Of course, we have scheduled another interesting video on C# + Microservices for tomorrow.
Salam Tural necesen ugurlar arzulayiram davami gelsin
Təşəkkür edirəm Anar!
Any plans on discussing ValueTasks?
Of course. After the next video