6 条评论

• ofrzeta 2小时前
  "I had heard the rumors that C++ was a scary language filled with footguns and segmentation faults, but I had never given it a fair chance myself" - props for this. There's too much hearsay in software engineering.
  [-]
  • fc417fc802 1小时前
    And then immediately afterwards we see const T* in a supposedly immutable data structure meaning the pointer remains mutable. Yet another classic footgun.
    [-]
    • mooreat 23分钟前
      It looked to me like most of the raw pointers in the blog were const. Sometimes you don't want the baggage of smart pointers and getting a cheap easily copyable view of your data is nice, so you want to return a const T. Usually if an API returns a const T I assume lifetimes are handled for me and that the ptr is valid as long as it is not nullptr.
• eps 2小时前
  Small nit, this - https://ryanjk5.github.io/assets/2026-05-14-GOLDE/torus.gif - is not what's conventionally referred to as a torus in CGoL. In torus left and right edges are also connected.
  [-]
  • xeyownt 2小时前
    Yes, it's more an infinite cylinder.
• jdw64 5小时前
  It seems like the thread_local CacheIndex only determines which cache to use, but it doesn't actually guarantee thread safety for concurrent access to the HashLifeCache itself. What would be a good solution for this?

  Should I use a mutex for each cache instance? As a beginner developer, my guess is that the original author assumes data races won't occur based on the execution timing. However, I'm really not sure if that assumption is actually correct/safe.

  [-]
  • nnevatie 49分钟前
    In my view, thread_local is a bit of a code/design red flag. I didn't read the entire code in this case to see whether the thread_local use is warranted or not, though.
• hiroakiaizawa 2小时前
  Interesting approach. I like that the implementation focuses on scalability rather than only visualization.
• ontouchstart 23分钟前
  This would be a cool template project to learn C++ without the pollution of LLM slop.
• classified 4小时前
  Fricking cool, I love it.