‹ BackHN Continuity

Thread

Platform-independent SIMD in Go

414 points · 152 comments · yurivish

  1. u8 · · focus · HN ↗
    This is why I love Go. Nobody was asking for this, but they took the time to do it right and continue to Push go as a memory safe, high-level systems language.
    1. __s · · focus · HN ↗
      go data races aren't memory safe
      1. shikck200 · · focus · HN ↗
        That does not make sense to me. Go is memory-safe, but it does not guarantee data-race freedom.

        So whats your point here? Haskell?

        1. amelius · · focus · HN ↗
          I suppose that if you create a map in one thread, and then access it from another thread, then that might cause segmentation faults? Because map is a type that is implemented in C.
          1. __s · · focus · HN ↗
            Yes, writing to maps isn't threadsafe, hence sync.Map. I learned this the hard way
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.