News for hackers. Stuff that matters.

A comment on How we tracked down a Go 1.24 memory regression.

Re:How we tracked down a Go 1.24 memory regression by nitinreddy88 on Thursday July 17, 2025 @10:03PM (#44600451)
I am more interested to learn about Swiss tables than bug fix :)

What are the best places to learn modern implementations of traditional data structures. Many of these utilise SIMD for last mile usage of modern hardware

[ Parent | on HN ]
Re:How we tracked down a Go 1.24 memory regression by gandem on Friday July 18, 2025 @12:08AM (#44601107)
OP here, I wrote another blog post that explains how Swiss Tables work, see https://news.ycombinator.com/item?id=44597562
[ Parent | on HN ]
Re:How we tracked down a Go 1.24 memory regression by skavi on Thursday July 17, 2025 @11:06PM (#44600808)
could read one of the implementations. there’s the original abseil implementation and rust’s in the hashbrown crate. probably many more.
[ Parent | on HN ]
Re:How we tracked down a Go 1.24 memory regression by woadwarrior01 on Saturday July 19, 2025 @03:14PM (#44618431)
I'd recommend reading the Swiss table design notes[1] in the Abseil documentation. You might also like F14 maps[2] from Folly.

[1]: https://abseil.io/about/design/swisstables

[2]: https://engineering.fb.com/2019/04/25/developer-tools/f14/

[ Parent | on HN ]
Re:How we tracked down a Go 1.24 memory regression by SkiFire13 on Saturday July 19, 2025 @03:34PM (#44618596)
In addition to this comment's siblings resources, I also suggest this really good Cppcon presentation on Swisstable https://www.youtube.com/watch?v=ncHmEUmJZf4
[ Parent | on HN ]