MONGOC_CLIENT...E_OPTS_DESTROY(3)

πŸ’… MONGOC_CLIENT...E_OPTS_DESTROY(3) β€” the cleanup era

okay bestie, listen up πŸ’– this one is from libmongoc and it's basically the graceful exit of the encryption-range-opts world. no drama, no leaks, just a clean little destroy call. periodt.


✨ SYNOPSIS ✨

void
mongoc_client_encryption_encrypt_range_opts_destroy (mongoc_client_encryption_encrypt_range_opts_t *range_opts);

New in version 1.24.0. πŸŽ€ (yes she's a newer girlie, respect her timeline)

So what does she actually do? She frees resources of a mongoc_client_encryption_encrypt_range_opts_t β€” but specifically one that was created with mongoc_client_encryption_encrypt_range_opts_new(). That's the match, okay? new() made it, destroy() cleans it up. iconic symmetry. πŸ¦‹

And the sweetest part: does nothing if NULL is passed. 🫢 no crash, no tantrum, no "bestie why". she just vibes and moves on. honestly? main character energy.


🌸 PARAMETERS 🌸

  • range_opts: A mongoc_client_encryption_encrypt_range_opts_t. that's the one getting the ✨cleanup treatment✨
πŸ’€ lowkey important: this is a destroy function, so don't go using range_opts after you hand it over. she's gone, she's freed, don't text her again.

πŸ‘€ SEE ALSO

  • mongoc_client_encryption_encrypt_range_opts_t β€” go meet the family, iykyk πŸ’œ

🌈 AUTHOR

MongoDB, Inc ✨

2009-present, MongoDB, Inc. β€” like, the whole era. we love longevity.


k byeee πŸ’–βœ¨ that was libmongoc version 2.5.6, dated Oct 09, 2026 β€” go forth and free your range_opts, bestie, no memory leaks in this group chat πŸ§šβ€β™€οΈπŸŒΈ

πŸ“¦ where this page comes from