{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiav53dgpg35eurxz2kdbq3d5u4kvxd5dt6z6euzyi6olbdsd5wnce",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3mgfflikzqi72"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreibwihra265zjspvlvm7krzfufy3mjp62tjliuyqlwlwz7inofm5ze"
    },
    "mimeType": "image/png",
    "size": 92594
  },
  "path": "/post/46767538",
  "publishedAt": "2026-03-06T11:22:45.000Z",
  "site": "https://programming.dev",
  "tags": [
    "Golang",
    "CodiUnicorn",
    "0 comments",
    "https://pvs-studio.com/en/blog/posts/go/1350/"
  ],
  "textContent": "submitted by CodiUnicorn to golang\n3 points | 0 comments\nhttps://pvs-studio.com/en/blog/posts/go/1350/\n\nGophers, hey. Confusing ^ with exponentiation instead of XOR in Go seems like a pretty easy mistake to make. The bug itself is simple, but it still shows up even in some well-known projects with large codebases.\n\nHow often does this happen in your code?",
  "title": "The operator ^ for exponentiation or for excluding: how not to confuse them?"
}