as a noob to golang, i’m clueless as to why slices need to exist. I’ve used arrays and lists all my coding life and never felt the urge to make anything resembling a slice to interface with my arrays. I can’t find a word on the internet about why go-slices need to exist. Can anyone point me at the…

Slices are of variable size, arrays are fixed size. Slices have a O(1) random access, Lists have O(n). An array with with n elements uses up n times the data size of memory. A slice the same + a pointer for the start and the current size. A List: one pointer per element! Thats why each of it does…

>Slices are of variable size, arrays are fixed size. I already know. Still clueless why slices are better than array references / pointers. >Slices have a O(1) random access, Lists have O(n). I don’t believe it. Why doesn’t every language dev in the world for every language ever invented, particu…

I consider dealing with slices in go or vec in rust much more ergonomic than dealing with arrays directly in C, where I always have to do a lot of manual book keeping when I want them dynamic, and therefore basically re-implement what is already known as slice on go or vec in rust. I know that rust…

[image] meemoeuk: Can anyone point me at the definitive and simplest base case example that cleanly shows slices being better in some useful way over straight array / list use. I would not say that it is a question of which one is better. Due to their different properties (arrays = fixed len…

Although I wish Go provided ways for much faster (unsafe scoped) code, I’ve never seen slices as a performance issue. I thought it’s just a similar concept for memory safety as Python had it. In safe blocks slices only shrink, the start to the right, the end to the left, it’s checked at runtime and …

Hi, @meemoeuk , and welcome to the forum! [image] meemoeuk: Can anyone point me at the definitive and simplest base case example that cleanly shows slices being better in some useful way over straight array / list use. No, I can’t give you anything definitive. It seems to me that slices only…

Hi all, The OP is right, slices are a little bit more expensive than arrays, his intuition is correct. But, you do not need to manually allocate memory (to resize) for a slice, and this is a huge advantage, as you need to write less code. A little bit more costly (but almost the same) and their ar…

I wrote a quick benchmark to illustrate the advantage of slices: [image] Go Playground - The Go Programming Language It creates a list of a million elements and then sums their value. It does the same with slices. % go test -bench . goos: darwin goarch: arm64…

I think of slices as a replacement for linked lists. I almost never use linked lists, or other methods, preferring slices. My background is mostly “C”. Creating slices is trivial, as is sorting them, though it would be nice to have a library search mechanism for sorted slices. I wrote an SPF al…

Yes, Go slices are what other languages call arrays (except for C, which uses pointers instead). So if the OP uses arrays and lists in other languages, he would find Go slices equally useful. I might ask why does Go have arrays (as it defines them), and why are they needed? I don’t think I’ve eve…

Go Forum

Noob is wondering why slices need to exist

Getting Help

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled