News for hackers. Stuff that matters.

A comment on The ups and downs of porting 50k lines of C++ to Go (2015). Parent comment

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by innagadadavida on Thursday March 14, 2019 @10:16AM (#19389387)
Did you read the update on Go 1.9? It is on par, I tried the benchmark on my machine why not try it yourself instead of downvoting?
[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by shaklee3 on Thursday March 14, 2019 @10:33AM (#19389555)
You aren't reading it correctly. The OP was saying it's not fair unless you compare against an unordered map. The update is referring to an ordered map which is much slower than an unordered. The GO math implementation, which is an unordered map, is still significantly slower than the C++ unordered map.
[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by detaro on Thursday March 14, 2019 @10:35AM (#19389574)
No, it's fairly clear that the update refers to the unordered maps case.
[ Parent | on HN ]