Oo(3)

✨ Oo(3) ✨ — OCaml library, bestie 💅

okay so this is the <pink>Oo</pink> page from the OCaml library manual, and it's literally all about Operations on objects 🎀. it's short, it's iconic, and honestly it ate.

---

🌸 NAME 🌸

Oo — operations on objects 🫶

---

🦋 Module 🦋

Module Oo ✨

no cap, that's the whole module line. she's minimal, she's mysterious, she's giving main character energy.

---

💖 Documentation 💖

Module Oo
 : sig end

so yeah — the module is Oo, and its signature lives between that sig and that end 🎀. cute little self-contained vibe.

Operations on objects — that's the whole tagline, and honestly? slay.

---

⭐ val copy : (< .. > as 'a) -> 'a

Oo.copy o returns a copy of object o — and by "copy" we mean a fresh object with the same methods and instance variables as o 💅. same fit, new body, iykyk.

⚠️ Alert unsynchronized_access. Unsynchronized accesses to mutable objects are a programming error. fr fr, do not come crying to me after you race two threads on the same mutable object 😭 — that's on you, bestie.

---

🔥 val id : < .. > -> int

returns an integer identifying this object, and it's unique for the current execution of the program 👑. it's basically the object's government name for this run only.

the generic comparison and hashing functions are based on this integer. so like, everything downstream leans on id — keep that in mind 🧠✨.

and here's the tea 🍓: when an object is obtained by unmarshaling, the id is refreshed, so it's different from the original object's id. as a consequence, the internal invariants of data structures such as hash table or sets containing objects are broken after unmarshaling the data structures 💀😭.

big warning energy: unmarshal an object that's sitting inside a hash table or a set and the invariants are toast. not me finding out the hard way. 🙈

---

that's it, that's the page — short but she served 💜. this was OCamldoc, dated 2026-06-22, footer Oo(3), and yes the doc said OCamldoc so we're crediting OCamldoc periodt 🌈✨. mwah, go write some objects 💋