The key thing to grok is: & = „address of” * = „value at” (of course apart from the * when used to declare a pointer variable 😉) Great animations BTW! 👍🏼🤩
Just started learning Go and I'm amazed that I could learn about Pointers in just 13 minutes. Amazing, never could really understand the idea of it in other languages, but did with easy with your explanation.
Just started learning golang after programming in python and javascript for over 6 years. I didn't study CS only IT, so all of this deep level stuff are very new to me, your explanation is super clear, I would recommend this video to people that are also starting out in golang
@@emmm_4465 same thing for me, coming from typescript and learn go, and find out go is interesting to play with, also solved some leetcodes using go, it was fun experience.
Nice Explanation. I know there were a long history of debate about "Passing as reference" and "Passing as value". The immunity is a another good angle to think this problem. Thanks so much. The animation is super clear.
Your explanation was spot-on, clarifying all the confusing parts, especially the puzzling matter of returning addresses versus copies. And your voice? It's soothing to the mind! Many thanks!
In Go *int is 2 tokens as in * int. The space is optional. I was also wondering if this subject is better suited to C instead of Go or, better yet, Forth or Assembly. Also, variable names get stripped when compiling normally. It's just address and type.
Hi! Really great job in the concise explanation! Got a like and new sub! One quick question though: Is the heap used when returning normal values as well or just for pointers? Does that heap allocation process happen everytime a function returns? Thank you in advance!
I been working with Go for so many years and, even knowing this stuff, is always good to refresh the mind. I have a question that might be due to not being a native, but I guess you said that we should use pointers for better usage of memory but this video proves different: ruclips.net/video/ISOjCvpNiYA/видео.html . Any opinion?
The key thing to grok is:
& = „address of”
* = „value at” (of course apart from the * when used to declare a pointer variable 😉)
Great animations BTW! 👍🏼🤩
Just started learning Go and I'm amazed that I could learn about Pointers in just 13 minutes. Amazing, never could really understand the idea of it in other languages, but did with easy with your explanation.
That's such a useful information in 13 minutes
thank you so much for the content
Just started learning golang after programming in python and javascript for over 6 years. I didn't study CS only IT, so all of this deep level stuff are very new to me, your explanation is super clear, I would recommend this video to people that are also starting out in golang
Right? This is a totally new paradigm for me also with JS background so super interesting. Think I wanna learn go
@@emmm_4465 same thing for me, coming from typescript and learn go, and find out go is interesting to play with, also solved some leetcodes using go, it was fun experience.
bless the youtube algorithm for this video
just perfect
Thank you for re-uploading this video. I thought it was going to be gone forever after your previous channel.
Outstanding explanation, thank you for taking your time.
I love the graphics shown, it helps a lot of 👍
Thanks for this video! You explained it very well. I tried a couple videos and I still couldn't get it till this video. Subscribed!
Bless this video
Very good and clear explanation.
Thank you for sharing the knowledge.
Nice Explanation. I know there were a long history of debate about "Passing as reference" and "Passing as value". The immunity is a another good angle to think this problem. Thanks so much. The animation is super clear.
Excellent explanation! Thanks.
I recently started learning Go and will definitely keep an eye on this channel! Such a nice explanation
Just the day after I start learning Go, thanks!!
Your explanation was spot-on, clarifying all the confusing parts, especially the puzzling matter of returning addresses versus copies. And your voice? It's soothing to the mind! Many thanks!
Really well explained! Amazing job!!! Thank you!!!
Great video, I just have a bit of experience with C and this was easy to follow:)
This channel deserves more subs, gj Jamie
Great Explanation.
Hey, your explanation was really really good!
I will look into more videos of yours :)
Really helpful explanation! Thanks
Nice and easy explanation, Thank you
Thanks. really good explanation.👏
In Go *int is 2 tokens as in * int. The space is optional. I was also wondering if this subject is better suited to C instead of Go or, better yet, Forth or Assembly. Also, variable names get stripped when compiling normally. It's just address and type.
great video, great animation. thanks
Please make videos on concurrency
Extremely helpful 😊
Awesome explanation. Thanks!!
interface, context, structs and functions plz
Nice
This isn’t the original channel…
what is the original?
Hi! Really great job in the concise explanation! Got a like and new sub!
One quick question though: Is the heap used when returning normal values as well or just for pointers? Does that heap allocation process happen everytime a function returns?
Thank you in advance!
Normally a copy of your returned variable will be returned to the calling frame on the stack.
Excellent explanation. May i know how did you make animation and show variable in box and lines what software or things?
canva
I been working with Go for so many years and, even knowing this stuff, is always good to refresh the mind. I have a question that might be due to not being a native, but I guess you said that we should use pointers for better usage of memory but this video proves different: ruclips.net/video/ISOjCvpNiYA/видео.html . Any opinion?
I am going tos leep. Goodbye. see you