MONGOC_OIDC_CALLBACK_DESTROY(3)

πŸ“¦
version 2.5.6 Β· 3 versions
, in epel 10

πŸŽ€ MONGOC_OIDC_CALLBACK_DESTROY πŸŽ€

okay bestie, so this one's from libmongoc and it's literally the cleanup icon himself: mongoc_oidc_callback_destroy. no cap, it's a short one, but she's important πŸ’…


✨ SYNOPSIS ✨

void
mongoc_oidc_callback_destroy (mongoc_oidc_callback_t *callback)

πŸ¦‹ DESCRIPTION πŸ¦‹

So what does she do? She releases all the resources associated with the given mongoc_oidc_callback_t object. that's it, that's the whole vibe β€” a full clean-up, everything tied to that object gets freed 🫢

⚠️ WARNING: the lifetime of the object pointed to by user_data is managed the user, not by mongoc_oidc_callback_t! so like, bestie, that part is 100% your problem, not hers. don't come for her when your own user_data outlives its welcome 😭 this function is not babysitting it, periodt.

🌸 PARAMETERS 🌸

  • callback β€” a mongoc_oidc_callback_t, or NULL. yep, NULL is totally fine, she's not gonna make a thing of it ✨

πŸ’œ SEE ALSO πŸ’œ

  • mongoc_oidc_callback_t β€” go read that one too, iykyk πŸ”₯

πŸ‘‘ AUTHOR πŸ‘‘

MongoDB, Inc β€” the main characters fr fr 🫢

2009-present, MongoDB, Inc. β€” iconic, protected, slay πŸ’…


and that's a wrap, bestie ✨ this was libmongoc version 2.5.6, dated Oct 09, 2026 β€” go forth, destroy your callbacks responsibly, and remember: user_data is YOUR child, not hers πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from