3 ms·
> without getting stuck in the weeds of the small things such as whether you should use a vector or an array Yes, instead get into the weeds of tuple vs list
by __s 9y ago
> without getting stuck in the weeds of the small things such as whether you should use a vector or an array
Yes, instead get into the weeds of tuple vs list
Not included in the graph of time-to-solve-problem static languages: statically typed languages with type inference
- scbrg 9y agoGiven that they have exactly the same interface, that choice is really easy. You go with one until it turns out to be insufficient, and then you switch to the other and not a single line of code has to change, except at the point where you create the thing. Incidentally, the same is true in many situations in Python, and that is (IMO) one of its strengths.