Re: clojure.spec origin story

>From clojure.spec - Rationale and overview : Almost nothing about spec is novel. See all the libraries mentioned above, RDF , as well as all the work done on various contract systems, such as Racket’s contra

Re: Rationale behind the naming and semantics for agents.

BTW I did not mean to imply you are wrong, just wanted to give some extra background. He specifically mentions: the problems of distributed programs are much harder - [...] *direct observation is not possible* [...] On Friday, 6 February 2015 13:21:52 UTC, Andre Richards wrote: > > Have

Re: Rationale behind the naming and semantics for agents.

Have a look here: http://clojure.org/state In the section *Message Passing and Actors*, he gives his reasoning. Basically, Actors were designed for distributed programs, but that comes with added complexity and a performance hit. He wanted a simpler model, because he was mainly concerned about

Re: {ANN} defun: A beautiful macro to define clojure functions with pattern match.

Don't think Rich Hickey is a fan of pattern matching, which is probably why it is not in core to begin with. If you watch his "Simple made easy" talk, pattern matching is one of the items listed under *Complexity Toolkit*, with this description: "Complects multiple who/what pairs". I'm not sur