Should we expose event-listener in this crate? about smol HOT 3 CLOSED

I personally feel that event-listener belongs in the same category as the utilities that are not currently exposed on smol rather than the various crates that are exposed on smol, but I have no strong opinion on this.

from smol.

I think there is a difference between event-listener and, say, concurrent-queue, which I personally think falls into the "shouldn't be exposed in smol" category.

If you look at the reverse dependencies for concurrent-queue, you can see that, outside of the crates used by smol, concurrent-queue is not used that often. In addition, concurrent-queue doesn't have much to do with async/await outside of its using in async/await crates.

In contrast, event-listener is heavily used outside of smol in crates like zbus and sqlx. In addition, event-listener is an important async/await primitive that directly ties into smol's goals.

from smol.

Deciding against

from smol.