How to handle cpu intensive code in core.async? Thread or fixedthreadpool for io bound tasks and for cpu bound?
the thread macro can be used to spin both long running cpu bound stuff and io stuff
the main thing is just don't block the threadpool used for running go blocks, so if you have any code that could run for a long time without doing any channel operations (yielding the thread back to the threadpool) it is a good idea to give that a dedicated thread