(doseq/lazy/interop)? problem, different behaviour when adding a println

Hi all, I'm working on solving the problem http://adventofcode.com/2016/day/11 , and ran into some weird behaviour. I have solved the actual problem, so let's not focus on it. Here's my code: (defn compute3 {:test (fn [] (is= (compute3 (create-state "F4 . . . . . "

Re: Faster diffing for large-ish nested data structures

Can Specter walk two sequences in lock-step? That's what's needed for a good diffing engine, and that seems quite far removed from Specter's design. On Fri, Apr 21, 2017 at 11:22 PM, Mars0i wrote: > This might be a job for which Specter is particularly useful. You might > have to dive pretty de

Re: Faster diffing for large-ish nested data structures

Not to speak for Nathan, but I asked in #specter and he indicated it's unlikely to help, which I imagine is primarily for the reason Tim mentioned :) (It bears repeating though: I was wrong about specter. It's awesome and Nathan is incredibly helpful.) lvh Sent from my iPhone > On Apr 22, 201

Re: Faster diffing for large-ish nested data structures

tbc++, lvh, I'm not surprised that Specter doesn't help. That seems reasonable. Although I have come up against Specter's limits, I've been surprised at what it can do, so as a non-expert I tend to err on the side of thinking that it might help if I don't know that it can't. -- You received t

clojure.spec explain and multi-arity functions with first optional argument

(require '[clojure.spec :as s]) (require '[clojure.spec.test :refer [instrument]]) (defn request ([url]) ([params url])) (s/fdef request :args (s/cat :params (s/? map?) :url string?)) (instrument `request) (request [] "") ExceptionInfo Call to #'user/request did not conform to spec: In: [0] v

Re: foo.spec?

Hi, It took a little longer than expected, but Speculation , a Ruby port of clojure.spec, is now in a good place. It has the main features of clojure.spec: validation, conforming, generation, and instrumentation. What's missing is an equivalent of `s/describ