Bro, I would have never known that I will finally understand how pointers, reference and dereference works by watching a Go tutorial.! (I am a JS dev). Thank you!
Omg! I learned pointers in my first year of university using C and never understood it completely or how it worked under the hood. You have made a difficult topic into an easier concept. Thank you for your content and the hard work you put in behind the scenes.
Al-Adab Al-Mufrad 1183 It is related that Abu Hurayra said, "I never sae al-Hasan without my eyes overflowing with tears. That is because the Prophet, may Allah bless him and grant him peace, went out one day and he found me in the mosque. He took my hand and I went along with him. He did not speak to me until we reached the market of Banu Qaynuqa'. He walked around it and looked. Then he left and I left with him until we reached the mosque. He sat down and wrapped himself in his garment. Then he said, 'Where is the little one? Call the little one to me.' Hasan came running and jumped into his lap. Then he put his hand in his beard. Then the Prophet, may Allah bless him and grant him peace, opened his mouth and put his mouth in his mouth. Then he said, O Allah, I love him, so love him and the one who loves him!'"
Awesome video, I enjoyed it a lot and learned a lot. At 8:30-ish I'd changed the diagram a bit such that the arrow from the "[pointer] under 0x0002" to be pointing to 0x0001 and not to value "tifa". This way it would be a bit more accurate and clearer as 0x0002 and 0x0003 will be pointing to the same address 0x0001.
I think you should add also interface types to the pointer group, but I guess, you'll handle them in a seperate video, because you can do so much with them.
If you understand Pointers, All after that is easy. And here is the easiest way to explain thanks gang, can you cover this. Functions (specifically closures) Interfaces And the Concurrency in golang.
One handy use of this is for passing around huge structs you. By using pointers you won't consume more memory by having the compiler create a copy of the struct. Consequently, this will potentially speed up performance because the struct doesn't have copies that need to be garbage collected after it becomes out of scope. I recommend not thinking too much about performance when it comes to pointers, it's far more likely you need to consider using it because you want to mutate the value at the pointer rather than for performance reasons.
Cause they are generally lighter, think about this scenario, if you have a name := "mario" or a novel := "lorem ipsum, lorem ipsum, lorem ipsum etc..." and a pointer to those, in the first case you might not need it cause is just a short string and you can copy it easily, but in the second case, copy it all the time can be expensive, so in that case a pointer does makes sense, even if it does reserve memory for the pointer is always less memory than copying the whole novel on each function call.
I dont know if this is right feeling but i feel like golang is becoming easy every time i try to learn it. Last time i cant even understand modules But yesterday it suddenly sinked in 🤣
I don’t see why not. But bear in mind that ampersand points to memory address and not value itself. If you want actual value then replace ampersand with an asterisk 👍🏾
