 So for every meet up we have a simple goal pop quiz to test your understanding of code. Okay this is the code so the question for today is to find out what's wrong with this. Tell me what's wrong with this code and give me the solution for fixing it. What is it supposed to do? It's supposed to print out values. In order? It's supposed to print out 123. Yeah 123. I think it's going to print out in what number? What number is it? Three. Why? Yeah because it's a concept, it's a closure. I mean you should pass it to the important function. Because the variable, I mean when you compile it, when the whole function will run at a certain time after you complete the loop. We get the current value which actually at the end of the array which is three. So we print three. Okay let's see. Yes so that is correct. This explanation is also sort of on point. Okay why don't you tell me the solution first. Then we can go through the reasoning for this. You can put the value inside the routine. Pass it to the function. Pass it to the function and also it at the bottom. So what do I pass? So what do I pass? Over there and also inside the open-close bracket. That one also. It should be okay. Oh yes. Can you see missing something? Define the type, sorry. It's based in. Sorry I'm a newbie. Correct. Do you want to explain why? For those who may be new to this. So the form, the V variable is actually reused. So which means for every go function it closes over the V variable. After the form, it will be three. Wait but could the go-go routine actually print out one or two? I mean is it undefined or? No it's always three because it's in order. So it always takes the last value that's passed to it in the follow. So the first go routine gets scheduled only after the loop ends. That will have to be true for three to always be printed. Yes, let's see. So I can keep running this and it will keep giving me three. It's very consistent. What are the thousand numbers? Does the first go routine still schedule after the follow ends? Ya, I think so. I mean it shouldn't make a difference whether it's a thousand or whether it's three numbers. I think. Okay because the follow doesn't give up control. The follow doesn't give up control. Ya so whereas if you write it like this you're telling the go function to you're putting the value on the stack so that when the go routine is called it calls the value that's put on the stack. Okay, great. That's all for the simple go-go podcast today. Okay, thank you for coming. Ya, today is a very small group. Usually we have more but thanks for coming. See you at the next meetup.