Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add loop macros and go-for comprehension. #2
Also extend some docs, add more tests and some notes. I would like to have some standardized way to do error handling and higher level operations on channels and hence developed similar macros (1). I have started to reimplement the for-comprehension with channels instead of seqs to significantly reduce boilerplate code fiddeling around the function-boundary limits of core.async (similar to your reduce>) (2). The for-comprehension is still not ideal, as it is mostly eager atm.
In general I would like to see some explicit syntactic pattern definition for the combination of <, >, !, ? and * to compose macro names for channel operations consistently. It would also be nice to integrate an erlang-like actor library, so that the macros prove consistent in a larger context. This is just an idea though.