IO::Lam...oop::POE(3)

🎀 NAME 🎀

okay so welcome to IO::Lam...oop::POE(3), bestie 💖 — this is the page for IO::Lambda::Loop::POE, the POE event loop for IO::Lambda. It’s a User Contributed Perl Documentation page, and it’s giving “backend machinery that knows exactly what it’s doing” energy, not “use me directly” energy. 💅

---

🦋 DESCRIPTION 🦋

This module is the event-loop implementation for IO::Lambda that’s built on top of the POE event loop. That’s literally its whole thing, no cap. ✨

It is not intended for direct use — so bestie, don’t go calling it like it’s the main character. It’s backstage crew with an earpiece. 🎧💜

---

🌸 LIMITATIONS 🌸

Heads-up, queen: POE is also a proxy event loop itself. Depending on the actual event loop module it uses, functionality of IO::Lambda might be limited. Like, the vibes can vary depending on what’s under the POE hood — that’s the whole caveat. 🫶

---

✨ SYNOPSIS ✨

Here’s the “please pick me explicitly” route:

use POE;
use IO::Lambda::Loop::POE; # explicitly select the event loop module
use IO::Lambda;

or, the environment-variable route:

setenv IO_LAMBDA_DEBUG=loop=POE

---

💀 BUGS 💀

Threads and forks seem to be not playing nicely together with POE. That’s the note — not “never,” not “always,” just “seem to be not playing nicely,” so keep that exact caveat, bestie. 😭

---

🌈 SEE ALSO 🌈

• POE — the event loop this whole page is about. 👑

---

💖 sign-off time: this page comes from perl v5.42.2, dated 2026-02-15, and it’s IO::Lam...oop::POE(3) — mwah, go be iconic. 💅🎀