Hey there, fellow Go newbies (or should I say Gophers-in-training🕧)! 🌱
Interfaces seemed like one of those mysterious, magical things that everyone...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
Go makes me love my job :)
Hey martin..indeed Go is the best language so far to work with especially while focusing on the back-end side..Looking foward to collaborate with you in any kind of projects you need assistance
reach me out thru my email : allangithaiga5@gmail.com
Best regards,
Allan Githaiga
This is true for services development in general, not just web backends, and those issues I used to find vexing (vendor caching, for offline builds, for example) are now long gone. It remains clean to read with long term stability in the compiler and ecosystem, so you don't have things constantly change and break every time you happen to do a newer build...
This article is one of the most useful I've read recently about GoLang, especially regarding interfaces. Thank you!
this article was one of the worst
All articles at this level, don't answer the question
“Why not use the original structure ?”
If you don't use an interface, you'd end up duplicating a lot of the same methods (like Area() and Perimeter()) across different structs. The benefit of the interface comes when you need to handle a diverse range of shapes without constantly worrying about the details of each one.
I too worry too much when working in Go. Thank you for this guide!
If I may ask how do you make your blog banners especially the Go character?
well i just modify them using UX tools like figma,miro or canva
great article @githaiga22 , this is a nice and fun way to explain interfaces.
Nice article, straight to the point.
Salut à tous.
Je suis développeur d'application Android et je viens juste de terminer mon application gratuite de philosophie.
J'aimerais avoir des testeurs pour m'aider à l'améliorer. Voici mon adresse mail :
Laminefalldeveloppeur@gmail.com
nice learning interface and struct diffrances
Just a heads up that you can add highlighting to the code blocks if you'd like. Just change:
... to specify the language:
More details in our editor guide!
for the full explanation of the example above i find this useful
youtube.com/watch?v=SX1gT5A9H-U
Great article! Thanks for the explanation.
Yep, you don't understand anything about Go interfaces. An interface is a type. You never used the interface you declared. You just called methods all named the same (Sound). And then you promoted the empty interface which is a really bad advice.
To add more context, fmt.Println accepts variadic 'any'. This code is not generic or templated. It has nothing to do with interfaces. It relies on Runtime Reflection, which is the slowest. I use it in my libs.