I'm certainly not privy to the nitty-gritty, but I'd encourage you to skim over the Go Dev team meeting notes. It's really cool to see what people have proposed over the years, how the team interacted with it, and ultimately why yes, why no. It's been really educational.
The short of it is Java. That's a joke, because Java isn't short. We don't need another Java. The result is that an idea has to be very, very, very good to be accepted and developed internally. In the meantime, you should check out this repo: https://github.com/Workiva/go-datastructures It hasn't changed much lately, but that's because, for its API, it's maybe mostly done. The issues are generally from bad expectations, and there isn't much to add. Generics means that some of them could be implemented differently, but that's more an indicator that better projects might exist nowadays. On Tuesday, April 12, 2022 at 1:19:22 AM UTC-5 Jack Li wrote: > Hi group, > > Why Go provides only 2 built-in data structures, slice and map. It has > just more than C, but less than all other programming languages I've heard > of, C++, Python, Swift, Rust. > > I think this simplicity attracts me very much. Sometimes I can use only > one data structures for a task. Because there is no more similar data > structures for choice. It's really "one way to do one thing". This also > makes code like familiar and consistent. > > I want to know more about the mind behind this design of built-in data > structures. > > Thanks > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/83056e21-39ee-4f0f-9f10-e40c17af152dn%40googlegroups.com.
