Malika Srivastava

Python Programmer | Go Noob | Sharing tidbits on Python and Go

Twitter = My Note Making App.
I tweet so I don’t forget what I just learned. 🙃

[Malika Srivastava @malika8code]

If you are a curious programmer, all roads lead to the kernel.
It may take a while to get there, but you will find yourself there eventually.

[Malika Srivastava @malika8code]

@architxkumar Lol yeah 😅
Got a bit cocky with my script, didnt run go vet or anything
In hindsight it feels so obvious like how can you even make that mistake
It is suchhh a basic af rule with waitgroup
I didnt even get as far as the debugger though 😂😂
The IDE warning called me out first 👀

[Malika Srivastava @malika8code]

Just sharing a subtle bug in my #golang script that taught me a lot about #goroutine scheduling & WaitGroup etiquette.

We wrote a script to start N #goroutines, but it ran intermittently.

Sometimes all tasks processed, sometimes only some.

[Malika Srivastava @malika8code]

Lesson learned.

1. Always call wg.Add() before launching the goroutine.
2. Use defer wg.Done() inside.

[Malika Srivastava @malika8code]

Interestingly VS IDE even warns about this!
…but only if wg.Add() is the very first line in the #goroutine. 🥲

Any loggers or other statements before it and the warning disappears.

This warning nudged me to restructure my code when I was testing a simpler version locally.

[Malika Srivastava @malika8code]

@anthdm What great timing! I was just reading about it today.

[Malika Srivastava @malika8code]

Quick Review of the book - Def a great read but not beginner friendly so would recommend completing your #golang basics before reading.

The book helped me understand how useful channels are for controlling Goroutines and visualize them.

Personal notes: https://t.co/knIJH9Dlef

[Malika Srivastava @malika8code]

Took me 3 months, but I FINALLYYY finished Concurrency in Go by Katherine Cox. 👩‍💻🥳

Shoutout to ALL the GopherCon Speakers, @k0dvb, @MadhavJivrajani, @karan_6864 & many more - your content helped me connect the dots whenever I got stuck! 🫶🫶

And of course, GPT too. 🤖
#golang

[GopherConIndia @GopherConIndia]

GCI Talks are now live on YouTube! Explore insightful sessions and gain valuable perspectives from industry experts.

Check out the complete playlist here: https://t.co/nXLXWKcZh6

Stay tuned – Flash Talks are coming soon!

#Gci24 #GopherconIndia2024

[Malika Srivastava @malika8code]

Summarized Key Differences in Behavior:

- Pointer Receiver (SafeWithdraw):
The same mutex is shared, ensuring proper mutual exclusion with sequential updates

- Value Receiver (Withdraw):
Each goroutine gets a copy of the mutex, can lead to race condition & inconsistent updates.

[Malika Srivastava @malika8code]

We have two functions; one with value receiver and another with pointer receiver.
The goal: Simulate concurrent withdrawals, where one goroutine might be blocked by another due to the mutex.

Playground: https://t.co/cud9fvUp2d

[Malika Srivastava @malika8code]

PFA the warning I encountered while exploring the behavior of the sync.Mutex package.

I understood using a value receiver for the Withdraw function isn’t ideal - it doesn’t update the original balance, but I wanted to dive deeper into how copied locks can disrupt synchronization

[Malika Srivastava @malika8code]

A thread on understanding why Go warns about 'passes lock by value' when dealing with sync.Mutex 🧵⬇️

👉 Prerequisite: A basic understanding of how sync.Mutex works for locking critical sections in concurrent programming. Ready? Let’s dive in! 🚀

[GopherConIndia @GopherConIndia]

Exciting announcement!

The GopherCon India 2024 talks will be available shortly on YouTube! Get ready for a series of insightful talks that dive deep into the latest trends, innovations, and best practices in the Go programming world.

Stay tuned for the release!
#GCI2024

[Malika Srivastava @malika8code]

@matryer How does item know its value in each loop iteration when we should have the final value as five?
What should I Google to understand this behavior better?
Is this immediate evaluation and delayed execution, meaning each loop has evaluated "item" BUT deferring the print execution?

[Malika Srivastava @malika8code]

Hi @matryer
Watching your talk on Defer from the London Gophers 2020 conf.
Im getting output as "ten nine eight.." and cant figure out what Im missing.
Can you help me understand if there’s a change in Go regarding defer function scope or closures? #golang
https://t.co/UYNhlI4vyI

[Malika Srivastava @malika8code]

@mi_ritik75 This helped me by @karan_6864
https://t.co/MCcV6DkLjO
Good Luck! :)

[Malika Srivastava @malika8code]

Spent the evening fixing a minor bug 🕵️‍♀️

But it led to a great learning moment.

Have a better understanding of function behavior wrt value vs. pointer arguments in #golang

Malika 🤝 Go's pointer & value receiver concepts.

[notABilliMachi @arora_tanya21]

sounds like someone like me was in charge of coding
#bookmyshow @bookmyshow #Coldplay

[Malika Srivastava @malika8code]

TIL that the order of fields in a struct can impact the struct's size and the memory cycles needed for access.
#golang

https://t.co/DjjBHNpEKx