Fork me on GitHub
#core-async
<
2016-05-26
>
noisesmith18:05:21

darwin: the limit there is the method size limit of the jvm - the macro simply generates more code than the vm can handle

noisesmith18:05:57

darwin: if it's a long series of ops, the simplest fix is probably to break out subsequences of ops into separate go blocks connected by channels to the top level block but started in parallel

danielcompton21:05:15

You could probably even thread -> the go blocks

danielcompton21:05:25

the return value of one go-block gets pumped into the next