This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-01
Channels
- # bangalore-clj (1)
- # beginners (16)
- # bigdata (1)
- # boot (16)
- # cljs-dev (79)
- # cljsjs (37)
- # cljsrn (62)
- # clojars (1)
- # clojure (260)
- # clojure-austin (3)
- # clojure-dev (3)
- # clojure-dusseldorf (3)
- # clojure-italy (1)
- # clojure-russia (32)
- # clojure-serbia (2)
- # clojure-spec (8)
- # clojure-uk (146)
- # clojure-ukraine (16)
- # clojurescript (66)
- # cursive (27)
- # datomic (57)
- # dirac (124)
- # emacs (10)
- # hoplon (12)
- # juxt (6)
- # keechma (6)
- # lein-figwheel (18)
- # leiningen (6)
- # lumo (51)
- # off-topic (1)
- # om (66)
- # onyx (41)
- # perun (1)
- # play-clj (1)
- # protorepl (9)
- # re-frame (20)
- # reagent (11)
- # ring (4)
- # ring-swagger (10)
- # rum (22)
- # specter (8)
- # sql (2)
- # test-check (5)
- # untangled (27)
- # yada (29)
@ghadi I believe it’s not a choice of registers vs locals. With a PEG parser you have ordered choice so I suppose than in (/ A B)
you first try to parse A then backtrack and try B. In Seqexp |
is non-deterministic so I have to represent concurrent “threads” (and deduplicate them). It’s in the deduplication part that determinism is brought back by keeping submatches of the “leftmost" (according to the choice tree) thread.
not possible to spec lambdas? i suppose you could validate it the body of the lambda via assert
depending what you mean, you can spec a function with fspec
after spec takes over the world for describing data - i hope rich, alex, et al take on session types / protocol specs 🙂
I'd love to see a spec-take on "isa?", "subset of?", etc.