Hey Techie!
Welcome to my Go series! I'll be sharing what I'm learning in ways that make sense to me, the mistakes I make and the "aha!" moments that help everything click. Whether you're learning Go too or just curious about it, I hope you'll pick up something along the way.
Feel free to add any insights or experiences in the comments.
Today's topic is... drumroll, please! Slices. Let's dive in!
So, what exactly is a slice?
When I first came across slices in Go, I thought they were another name for arrays. Turns out, they're not!
A slice is a dynamic view into an underlying array. It is internally represented by a small data structure called a slice header. Instead of storing the elements themselves, the slice header stores a pointer to the underlying array, along with its length and capacity. This realization helped me understand why modifying a slice can also modify the original array.
Another interesting and convenient thing is how flexible slices are compared to arrays which are fixed size. Slices can grow using functions like append() or be resliced to work with a smaller portion of the underlying array. This flexibility is one of the reasons slices are used so frequently in Go.
A little heads up, I used AI to clean up my grammar and typos. The technical ideas and thoughts in this article are 100% my own.
