{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiai5o3yxobeeqfhovyonico62mck6kbccs5adpqj2wraqvethnoii",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkwugcljyw42"
  },
  "path": "/t/bitslice-or-a-sound-way-to-implement-one/24194#post_14",
  "publishedAt": "2026-05-03T08:05:44.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Yeah, it's an interesting idea for a greenfield language (and maybe greenfield CPU). Treating bits as non-independent parts of a byte doesn't _really_ feel different to me from treating bytes as non-independent parts of a word, and that was definitely a thing for a long time. And 64-bit address spaces are BIG, dividing the maximum size by 8 isn't really a problem. I guess that might be a downside for smaller address spaces, that you either need two kinds of pointers or a relatively low max memory limit to fit that extra addressing in.",
  "title": "`BitSlice` or a sound way to implement one"
}