Clojurians Log v2

The ring-core-protocols library is designed to have zero dependencies, and adding an implementation for core.async channels would add a dependency on core.async. However, please feel free to create your own library that adds an implementation.

Sure. Out of interest having never designed a popular core library like this, why is that important, given that users will typically use ring-core-protocols together with the rest of ring, which does have some dependencies?

Because sometimes they don't. For example, http-kit has a goal of having no dependencies. We shouldn't force people to include dependencies that aren't necessary, particularly for mandatory elements of the Ring SPEC.

Splitting ring-core-protocols from ring-core was as a result of user feedback.

That's very enlightening thanks