It does everything that core.async does (in fact, it even has a compatible interface) and more. Most notably, you can block with any arbitrary function, not ju

It does everything that core.async does (in fact, it even has a compatible interface) and more. Most notably, you can block with any arbitrary function, not just the specially-designated parking functions in core.async. Furthermore, they need not be visible to the go macro, unlike core.async (so you can call them in a compiled closure, for example, and it will just work).