Your computer, your rules.

Commonly done when abstracting resource handles across GPU APIs

Why even cast it to an integer? Can't you directly use a pointer as an identifier?

Potential overflow and point to wrong spot

Can ask the question in small brain language instead?

What could go wrong, using a pointer to a web page as your social web identity? Answer: Indieweb, Mastodon, verifiable claims and other silos.

https://nostr.build/i/5899616ca3b20638ec2c507ef3e718a578555131f415b58d7bfa1befab3998cd.jpg

I would worry about collisions. The object with the id could livee longer than then pointer. When the memmory is free again we might have a new different object at the same point in memmory...

The possibility of collision is very high. You should use an uuid