Re:Ten Years of “Go: The Good, the Bad, and the Meh
by valenterry on Tuesday July 18, 2023 @03:47PM
(#36778191)
It's not about creating a tree map, it's just about using one. Maybe even one provided by a library, doesn't matter. I'm sure that 95% of the developers will need a tree map at least once in their career.
[ Parent
| on HN ]
Re:Ten Years of “Go: The Good, the Bad, and the Meh
by Veraticus on Tuesday July 18, 2023 @04:03PM
(#36778356)
I've been using Golang professionally for about a decade. In that time the only place I've ever needed to use a tree map was an interview that specifically called for it.
Whose usage are you trying to optimize the language for? Golang is not a good academic language. But it is extremely good for actually solving problems with code.
Re:Ten Years of “Go: The Good, the Bad, and the Meh
by Mawr on Tuesday July 18, 2023 @05:43PM
(#36779492)
A tree map is just an example.
More compelling ones are sets, ordered maps, a generic sync.Map, optionals (nulls suck!), abstractions over channels - badly needed!
I wouldn't consider any of those to be academic.