Thank you so much for such a wonderful content and explanation. This is what is missing out there in so many Golang videos I have seen on youtube. This is a real time stuff. Without this deeper understanding all the code out there in packages written by other and I want to consume them, I will have no idea what to look for or how to use those wonderful stuff in my code. I would appreciate if you can make one video taking us into the world of real time coding, may be you can explain writing a program of your own using some 3rd party library out there. Please teach us on where to start while going through the package and how to understand someone else package so we can start implementing the required features into our code
Thank you Matt, your video is very useful! I'm a little bit confused about object literal. At 14:41, We know that within a function, local variable is put on the stack, but where is Point literal (i.e. Point{1,1}) stored if that's not addressable (is that in Register, I guess)?
I like how all the advice I've seen is avoid interface{}, even Rob Pike gave a talk saying avoid it and every single go project I pull uses it extensively😅
Extremely useful around min 15:00. Is it addressable? If you have seen it only on the right hand side of an assignment expression, it is not addressable.
I don't know. I still feel that if Go used required explicit pointer dereferencing and used 'dot' notation vs 'arrow' notation to differentiate methods from pointers and aactual objects, it would have been clearer than doing all of this work under the hood. For me, it is not much of a beneficial abstraction.
Would love more videos. Your teaching style is great. Please consider uploading and helping the newbies
Just another awesome class!
This lecture series is by far the best resource to learn go.
The professor is awesome, the master
Thank you so much for such a wonderful content and explanation. This is what is missing out there in so many Golang videos I have seen on youtube. This is a real time stuff. Without this deeper understanding all the code out there in packages written by other and I want to consume them, I will have no idea what to look for or how to use those wonderful stuff in my code. I would appreciate if you can make one video taking us into the world of real time coding, may be you can explain writing a program of your own using some 3rd party library out there. Please teach us on where to start while going through the package and how to understand someone else package so we can start implementing the required features into our code
Thank you Matt, your video is very useful!
I'm a little bit confused about object literal. At 14:41, We know that within a function, local variable is put on the stack, but where is Point literal (i.e. Point{1,1}) stored if that's not addressable (is that in Register, I guess)?
I like how all the advice I've seen is avoid interface{}, even Rob Pike gave a talk saying avoid it and every single go project I pull uses it extensively😅
Extremely useful around min 15:00.
Is it addressable? If you have seen it only on the right hand side of an assignment expression, it is not addressable.
I don't know. I still feel that if Go used required explicit pointer dereferencing and used 'dot' notation vs 'arrow' notation to differentiate methods from pointers and aactual objects, it would have been clearer than doing all of this work under the hood. For me, it is not much of a beneficial abstraction.