You can't make C++ not ugly, but you can't not try (2010)

Re:You can't make C++ not ugly, but you can't not try (2010) by steerablesafe on Thursday February 27, 2020 @04:25AM (#22431867)

abseil's might have a similar API but it's most definitely not the same (function signatures looking the same doesn't make it the same API). Some of the standard containers can't be fast because too strict/specific standard requirements, not because they don't try hard enough.

Having said that I think using abseil's containers is reasonable, even as a default, if you can afford the dependency.

> std::unordered_map

AFAIK unordered_map is the most awful of all standard containers.

[ Parent | on HN ]

Re:You can't make C++ not ugly, but you can't not try (2010) by leetcrew on Thursday February 27, 2020 @07:38AM (#22432685)

what's wrong with unordered_map? it's at least more useful than map.

[ Parent | on HN ]

Re:You can't make C++ not ugly, but you can't not try (2010) by aw1621107 on Thursday February 27, 2020 @10:46AM (#22434248)

From what I understand its API is overspecified to the point that it basically forces a "traditional" array-of-linked-buckets implementation, which can be horribly slow on modern processors due to the need to chase pointers. This means a lot of the potential performance improvements of allowing map elements to be unordered are lost.

[ Parent | on HN ]