On Wednesday, 16 May 2012 at 07:05:29 UTC, Anders Sjögren wrote:
For carefully profiled code, that can be a disadvantage
Either that, or just the plain algorithm. Then the issue isn't profiling -- it's the time complexity.
e.g. You can't simply "pretend" it's doing the best thing possible, because libraries never get it right *all* the time. So IMHO saying /how/ to do it is a lot more useful than /what/ to do, since it lets you choose whether your algorithm is O(log(n)) vs. O(n) vs. O(1).
(Yes, this means I don't like C++'s std::map or std::unordered_set either, because they tell you nothing about the time complexity. Java did it correct there.)
