Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
The goal of core.async is to decouple producers and consumers of information in software, without dictating specific thread or blocking semantics, and without introducing callback hell. Also, to do all of this as a library, portable anywhere you can run a dialect of Clojure.
core.async builds upon the work done with Communicating Sequential Processes, and provides:
- facilities for independent threads of activity, communicating via queue-like channels
- both real threads and shared use of thread pools (in any combination), as well as ClojureScript on JS engines
What We Will Cover
In this talk, we will cover the design of core.async, and then move directly to exploring core.async's capabilities:
- Creating unbuffered and buffered channels
- Threaded put
goblocks to invert control, achieving async without threads
- IOC put
- Simultaneously waiting for multiple operations with
- Timeouts as "just another kind of channel"
Finally, we will assemble these primitives into substantial working programs, building toward the Holy Grail of async: substantial UI application development in the browser, with no callbacks in sight.