4 ms·
Use slices. Really, maybe we should remove container/* completely, so we don't have to answer this stuff over and over again.
by luriel 14y ago
Use slices.
Really, maybe we should remove container/* completely, so we don't have to answer this stuff over and over again.
- qznc 14y agoSlice still restricts you to an array data structure (a continuous block of memory). How would you implement a sorted set in Go? It should be generic and type safe and efficient, please. Compare with the C++ solution.
- draven 14y agoI think the problem with saying that Go can be used as a C++ replacement is that the statement is too vague. The problem space in which Go is a great tool and the one in which C++ is a great solution have a big overlap. But that does not mean that you will solve a given problem in this overlapping space the same way. Both languages have a different set of trade-offs. If you need a typesafe, generic sorted set with strict efficiency needs (or things like precise control over memory layout and such) then by all means go for C++, it's been designed for that kind of constraints.
- luriel 14y ago> If you need a typesafe, generic sorted set with strict efficiency needs When people ask for things like this, I can't help to think that what they want is not generic at all, they want something very specific to the problem they are solving, in those cases just writing custom data structures is the way to go in any language anyway. It is the way it has been done in C for decades too.
- kragen 14y agoYou may be able to write the custom data structures more easily with the STL than in C.