Hello! I'm trying to wrap my head around pipeline and pipeline-blocking. How exactly we are going to execute parallelism if operations are blocking? Or what does it mean that it's (pipeline-blocking) for blocking operations?

it's for cases where the parallelized code might block its own thread

eg. it does IO without an async IO wrapper

your original thread (the one that calls pipeline-blocking) is not blocked, but the difference is which kind of context the parallel code should run in

so pipeline or pipeline-async are safe for code that is async (and you want it to run in multiple async blocks), and pipeline-blocking is for code that would hog the thread, so it needs a (more expensive) thread from a different pool

since core.async only uses 8 threads in its pool by default, you need to be careful not to starve it by blocking its threads

hope that's clear

>eg. it does IO without an async IO wrapper

this one is clear 😅 Thank you!

@troglotit It took me a while to understand as well but make sure you use pipeline-blocking for an deref/`@ `. It seems obvious but I often tripped over my code deadlocking so "no reason" even though I was at fault.