al_destroy_mutex(3)

💅 al_destroy_mutex — Allegro 5 API 🎀

okay bestie, so you've got a mutex and you're done with it, and now you need to let it go. This is the manual page for al_destroy_mutex from the Allegro 5 API, and honestly? it's giving cleanup era ✨

---

✨ SYNOPSIS ✨

#include <allegro5/allegro.h>

void al_destroy_mutex(ALLEGRO_MUTEX *mutex)

one function, one pointer, zero drama (as long as you read the description, which you will, because I said so 🫶)

---

🌸 DESCRIPTION 🌸

So what this does is free the resources used by the mutex. That's it, that's the whole job. Your mutex had a little life, it held some memory, and now you're releasing it back into the void. Iconic behavior, no notes 💖

But — and this is the part where you listen to me — the mutex should be unlocked when you do this. Like, unlocked-unlocked. If you go ahead and destroy a locked mutex anyway? Destroying a locked mutex results in undefined behaviour. Not "a warning", not "a little oopsie", not "the library will be nice about it". Undefined behaviour. The kind where your program can do literally anything and you cannot be mad about it 😭 so please, for the love of everything, unlock it first. Vibe check your mutex before you end it 💀

Also super important and lowkey kind of sweet: if mutex is NULL, the function does nothing at all. No crash, no explosion, no problem. It just looks at the NULL and goes "ok bestie, nothing to do here" and moves on ✨

⚠️ quick recap for the people in the back: unlock the mutex first, and remember that destroying a locked mutex = undefined behaviour. NULL is totally fine and does nothing. 🎀

---

🦋 SEE ALSO 🦋

Honestly the original page doesn't send you anywhere else — no cross-references, no extra reading. You got the whole thing right here, bestie 👑

---

and that's the whole page!! Allegro reference manual energy, al_destroy_mutex(3), brought to you by the Allegro reference manual ✨ go unlock that mutex and live your best life, mwah 💜🫶