Pointers took me some time to wrap my head around.
Also, coming from Ruby where interfaces are more of an implicit concept, having to define them explicitly in Go was frustrating at first.
Interesting, implicit concept like how you pass in a Ruby value and it runs methods that are expected to be there?
Yeah, the idea of duck typing, where as long as an object responds to certain methods and had certain values it can be replaced with any other object, no matter the type, that implements the same methods and properties, without that interface having to be explicitly defined anywhere.
When I was doing Ruby I used to love the flexibility that me, now I can't imagine how anyone can maintain that lol.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.