I don&#x27;t think that go as people tend to use it really benefits from vectorized code. Most people who are using go that I interact with are not writing numerical processing code but network servers and business logic for high level web APIs. You might get minor speed ups in vectorized memcpy but I can&#x27;t see much else.<p>I imagine the most important CPU features for most go code would be a good branch predictor and fast atomics &#x2F; synchronization primitives.<p>If you&#x27;re using go for numerical processing code I&#x27;d like to hear more about it. Mostly because it&#x27;s kind of a PITA.