=20 > I noticed that isEmptyChan blocks if the channel is already > waited on by readChan, is this the intended behaviour? > At least I was a bit surprised by a blocking predicate.. I agree this doesn't seem right. Looking at the implementation though, I can't see an easy way to fix it - any suggestions? Cheers, Simon