Idiomatic Go Set
Notes on implementing a Set while migrating from JavaScript to Go — using maps to represent Sets since Go lacks a native Set.
Notes on implementing a Set while migrating from JavaScript to Go — using maps to represent Sets since Go lacks a native Set.
Using Go 1.16's embed to include files at compile time, avoiding path/environment issues. Not suitable if files must change at runtime.
From JS to Go, I wasn't familiar with Go's approach to modularity. Although similar in places, Go's simple and opinionated design is very evident.
Revisiting serialization/deserialization in Go and the origin of "Marshal", building on my earlier post about struct tags and reflect.
Context is added to Go standard library in 1.7. It's primarily used for including deadlines, cancellation signals, and passing request-scoped values.
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.