Thank you so much Sir for such a great effort in explaining everything so well and precise. I been studying your lectures since the beginning of the first class, and i really loved and enjoyed them. I had finished some of the golang courses in Udemy and Coursera, but i learned much better from your class, not only that you dig down to every core concepts, but also pointing out those gotcha moments. I'm grateful I found your channel!
I would like to tell the same thing that some people write down below: this is what is called a "teaching"!!! When you listen and understand, when you feel the pause, when you have a time to absorb the knowledge! Very well done, you are my one of the BEST teachers, Matt!
This video is a gem. I'm surprised by how well it is crafted and well organized. I'm going to recommend this channel to my all colleagues. Thank you, sir.
I have watched 4 Golang Course in the last 3 months and I have learned a lot but this Course is beyond anything out there. So comprehensive, everything explained in detail and in a way that even a newbie like me can understand it. fabulous work. well done man.
I tested it out myself and it works the same. The ctx.Done() channel can be read as many times as you want as a cancel call basically closes this channel. So reading from it in the get function and returning will also clear out those hanging go routines
Hello Matt. Your videos are amazing. I was wondering why we need to read ctx.Done() inside select as we already passing ctx to the get func and that func is attaching it with request to make do call. When context from any parent func is getting cancelled/timed out do is knowing that and returning with error, right? And we are receiving that error in the results chanel.
Well, if a subtree would be created with a longer timeout than it's parent it would never reach that timeout, since it will be cancelled from above. Nevertheless, a subtree may have a shorter timeout, i.e., reach deadline before it's parent does if necessary.
This is what I call teaching. High quality contents, very well delivered. Thanks a lot Matt.
Glad you enjoyed it!
Its like Learning from Creators of Golang. I wish Rob Pike Would have explained these things in YT but anyway we have Matt.
In an era of techbro influencers overhyping and under-explaining everything, this content is absolutely invaluable. Thank you!
Lol hahahaha
Very true
TechoBro Influencers are just selling Dreams not knowledge.
Thank you so much Sir for such a great effort in explaining everything so well and precise. I been studying your lectures since the beginning of the first class, and i really loved and enjoyed them. I had finished some of the golang courses in Udemy and Coursera, but i learned much better from your class, not only that you dig down to every core concepts, but also pointing out those gotcha moments. I'm grateful I found your channel!
You're most welcome!
I would like to tell the same thing that some people write down below: this is what is called a "teaching"!!! When you listen and understand, when you feel the pause, when you have a time to absorb the knowledge! Very well done, you are my one of the BEST teachers, Matt!
I had the pleasure of exploring golang by going through dozens of tutorials, but this tutorials from first class is a Gold mine for golang developers.
Think I have not found a better explanation than this on the whole Internet for this topic. Excellent content!
This video is a gem. I'm surprised by how well it is crafted and well organized. I'm going to recommend this channel to my all colleagues. Thank you, sir.
this is probably the best go lang series on youtube
Your teaching style is very effective, love the content, keep it up!
this channel is so underrated, I hope you get more views. Great content.
I have watched 4 Golang Course in the last 3 months and I have learned a lot but this Course is beyond anything out there. So comprehensive, everything explained in detail and in a way that even a newbie like me can understand it. fabulous work. well done man.
Excellent presentation, like all your other presentations, practical, complete, to the point and precise. Thank you very much!
This course have helped me immensely so far!
Holy moly. This is quality!
10/10, best explanation of context in go
Thanks for these videos Matt. Lovely content
Outstanding course
good explanation teacher Matt
Great method of teaching .... really appriciable...
Amazing explanation
Thanks Matt. Sending Pranams 🙏
First of all , thank you so much Sir for this high quality content, i just want to say that adding a "case
I tested it out myself and it works the same. The ctx.Done() channel can be read as many times as you want as a cancel call basically closes this channel. So reading from it in the get function and returning will also clear out those hanging go routines
also closing the results channel after getting the result will clear the waiting go routines.
More videos on Go or Comp. Sci please!
love it, thank you sir
You are very welcome
Amazing! Thank you very much
Excellent presentation , complete and precise. I was wondering could 'get' should handle
Not needed, as Do(req) will return an error on timeout
Great video!
26:14 why did the localhost request not tick
Hello Matt. Your videos are amazing. I was wondering why we need to read ctx.Done() inside select as we already passing ctx to the get func and that func is attaching it with request to make do call. When context from any parent func is getting cancelled/timed out do is knowing that and returning with error, right? And we are receiving that error in the results chanel.
"A subtree may be created with a shorter timeout (but no longer)"
What is this about?
Well, if a subtree would be created with a longer timeout than it's parent it would never reach that timeout, since it will be cancelled from above. Nevertheless, a subtree may have a shorter timeout, i.e., reach deadline before it's parent does if necessary.
you are awesome.
excellent talk!
Very good. Thanks
is Context garbage collected?
Http sockets do not exist
Too much talk, too little code visual imho