Threadwell

Recent Notes

  • Threads

    Aug 25, 2026

    • archive
  • nicbarkeragain

    Aug 25, 2026

    • archive
    • twitter
    • nicbarkeragain
  • vkrajacic

    Aug 25, 2026

    • archive
    • twitter
    • vkrajacic
Home

❯

Archive

❯

Threads

❯

valigo

❯

When it comes to pointers, "just use 64 bit integer" is way more intuitive to me.

❯

@valigo Interestingly, if you try to write Rust in this way, pointer provenance will cause misoptimizations that break everything.

@valigo Interestingly, if you try to write Rust in this way, pointer provenance will cause misoptimizations that break everything.

Properties5
typearchive
sourcetwitter
date2025-11-25
tagsarchive, twitter, valigo
description@valigo Interestingly, if you try to write Rust in this way, pointer provenance will cause misoptimizations that break everything.

Nov 25, 20251 min read

  • archive
  • twitter
  • valigo

Source

  • URL: https://x.com/levs57/status/1993312449379127742
  • Author: 🏴 LevS (of ether) 🏴 💙💛🇮🇱☀️🦁🗡️ (@levs57)
  • Posted: 2025-11-25 13:34:56

Branch

1/ @levs57

@valigo

Interestingly, if you try to write Rust in this way, pointer provenance will cause misoptimizations that break everything.

Related

  • Spine: 2025-11-17-when-it-comes-to-pointers-just-use-64-bit-integer

Graph View

  • Source
  • Branch
  • Related

Backlinks

  • When it comes to pointers, "just use 64 bit integer" is way more intuitive to me.

Created with Quartz v5.0.0 © 2026

  • GitHub