Understanding Contexts in Go in 5(-ish?) Minutes

✅ Subscribe and hit that 🔔 to get notified for all the latest tutorials!

🎥 Recording Setup

[eduardozepeda]

I searched for tutorials about go's context and yours was the only one I understood. Thank you so much.

[liang]

Nicely explained. I like how the video started with "what and why", and give a brief overview of the concept!

[fuadadio]

Finally understood this concept. Thank you so much.

[KoltPenny]

I want my $0.00001 from the ads back 😆. Great video, keep it up.

[TomDoesTech]

So early it's still in 360p :) Great video!

[cariyaputta]

Would you please cover the case of context use with grpc? Like how does the grpc lib make use of context, or how to use it for auth ...

[Nuraddinhassan]

your are my friend make my love golang, you are really great teacher, 😇🙂

[adedoyinphilip]

Thank you for this. Quite explanatory! 🙏

[m_]

It's very helpful. Thank you so much for the effort.

[keivinc]

thank you for the very good explanation 😀

[kevinkkirimii]

A question 10:40 is there need for the select case at line 35 since ctx.done() blocks and will be invoked once the timeout has exceeded ?!

[HasanAYousef]

Great and simple, a side question, what is the theme you are using at VS code?

[zawkhaled]

Definitely removed some of the confusion!

[gonzariosm]

Great example, thanks a lot for the info :D

[garryhall]

something that caused a little bit of confusion to me: the `<-ctx.Done()` on line 35 is actually blocking the code from continuing. In this particular case, , there is no need for the "select" but I understand that it could be useful in instances where there are multiple channels

[DiegoGago]

I've always wondered if sending information or adding logic via context is not a kind of hidden dependency in my code. Some people consider it a bad practice.

[pb]

Wouldn’t it make sense to pass context by pointer?

[davidjdriver]

This is one part of go I really don't get. It hides dependencies inside a super parameter. If your method needs to know something it should be explicit or in scope of the struct as a base config. Putting values into a dictionary and passing the dictionary around hides the dependency. I don't understand how this became used in Go at all as it is actually an anti-pattern.

[TechEats]

This audio is not clear. would be great if you can add subtitles

[mwnkt]

i kinda understand context. though still not so clear.