Race Condition in golang

Рет қаралды 19,802

Күн бұрын

Welcome to a youtube channel dedicated to programming and coding related tutorials. We talk about tech, write code, discuss about cloud and devops. That’s what we do all day, all year. We roll out a lot of series and videos on our channel.
All the learning resources such as code files, documentations, articles and community discussions are available on our website:
chaicode.com/
You can find our discord link, github link etc on the above website.
Twitter/X link: x.com/hiteshdotcom
Discord link: hitesh.ai/discord
Learn React with 10 projects: • Let's learn react from...
Learn Docker: • A practical guide on D...
Learn Kubernetes: • Complete Kubernetes Co...
How does a browser works: • How does a browser wor...
How nodejs works: • How node JS works | En...
Learn Redux-toolkit: • Learn Redux Toolkit in...
Learn NextJS: • Nextjs Full stack course
Learn Typescript: • Why to learn Typescript
Learn Javascript: • Welcome to new JavaScr...
Learn React Native: • React Native Mastery: ...
Learn Zustand: • React state management...
Learn Golang: • How to get started wit...

Пікірлер: 24

@bjugdbjk Жыл бұрын

this s the difference ..Mutex holds a lock for both reads and writes, whereas RwLock treats reads and writes differently, allowing for multiple read locks to be taken in parallel but requiring exclusive access for write locks.

@danielvega646 Ай бұрын

Which means... On RwLock multiple goroutines can read the resource but only one can write it?

@savjanismit7129 Жыл бұрын

Line no: 16 @Hitesh sir... It should be wg.Add(3) -> wg.Add(4) Because it might be chance that race condition occurs Also I've generated race condition by using wg.Add(3)

@faridshaik Ай бұрын

thanks

@sandip_patel_ 2 жыл бұрын

Great

@user-ys9kv3qz1n 6 ай бұрын

Hey Hitesh, shouldn't we place the resource as a different struct outside main ?

@mrrishiraj88 2 жыл бұрын

Namaste 🙏

@codedusting Жыл бұрын

go run --race . command no longer works in 2023. Gives error: go: -race requires cgo; enable cgo by setting CGO_ENABLED=

@mostafamohamedsalahelsouif5607 2 жыл бұрын

Hello, I am a beginner in golang. Can I know how to deep into this language. I find hard to learn from packages

@thisisdenish Жыл бұрын

creating thank . this video Hello so you for much sir

@jugama95 2 жыл бұрын

Groso! Thanks.

@3x10.8_ms 10 ай бұрын

okay! that means if one goroutine is writing something another goroutine will have to wait until the first one is finished writing...am i correct?

@mridulbagla 2 жыл бұрын

What is the use of the 2nd argument in the function which is m(m *sync.Mutex) because inside the function we are using mut(mut *sync.Mutex) which is already globally declared?

@MunshiWahid 2 жыл бұрын

I think it's an unintentional mistake. Using the function parameter "m" would be the more correct one. The example was working because the variables are in same lexical scope.

@baxiry. 2 жыл бұрын

There is no mistake. "m" here is not a parameter pass. Rather, it is a definition of the function. or signature of the function. Whereas "mut" from the global variable is a parameter to be passed in order to call the function. Imagine this code like this: func myfunc(m *sync.Mutex){ // bla bla } myfunc(mut)

@MunshiWahid 2 жыл бұрын

@@baxiry. Thank you. You are right.

@dhanushs1802 2 жыл бұрын

It's more for understanding than a use case i guess 1. If we initialize the waitGroup with a pointer &sync.WaitGroup{}, we don't need to pass the address when passing it to a function. Ex: //If wg was not a pointer when you initialized it as below, then see the argument passed to the function wg := sync.WaitGroup() go func(wg *sync.WaitGroup) { ... } (&wg) 2. It an IIFE but most of the time we will have a function declaration outside the main function and wg is initialized inside the main function so it cannot be accessed in the other function, unless we pass it as an argument.

@rafae5902 2 жыл бұрын

You are indeed correct. For the first variable, wg, the functions are probably using the one declared the function's scope, as it's kinda of overwriting the one in the main function scope. But for the second variable, m, you are correct that it's not being used and therefore is redundant.

@user-nl3uu9cx3x 3 ай бұрын

Shouldn't be m.RLock and m.RUnclock inside the function?

@tricepsbrachii 2 жыл бұрын

How can you use this in a real application, and not this kind of toy example? For instance to check for race conditions every time you run the build pipeline?

@justiceessiel6123 7 ай бұрын

I would say its more of preventing race conditions than implementing race conditions .. example if you are writing a test script like the way we do in node with jest and you have to spin up a database to run the test