String Handling in Go Using Rune
When indexing position `n` in a Go string, why isn't the `n`th character returned? In Go, you get a "Rune"; direct indexing gets you a byte.
When indexing position `n` in a Go string, why isn't the `n`th character returned? In Go, you get a "Rune"; direct indexing gets you a byte.
When interacting with MongoDB, I encountered unfamiliar syntax in Struct fields. This article explores why Go Struct Tags exist and the problems they solve.
In Go, there are two common data structures for "sequence data": Array and Slice. They are similar in syntax, but the differences in behavior.
Understanding "Polymorphism" is like "doing something, but the way it is done varies" For example, various "shapes" can "calculate area,"
The first time you see a Go Receiver function, you might wonder what this strange syntax is, with parameters accepted before the function name?
Go's design has all values passed by value; to achieve passing by reference effect, Pointer must be used explicitly.