This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-20
Channels
- # alda (2)
- # beginners (6)
- # boot (25)
- # cider (10)
- # clojars (5)
- # clojure (81)
- # clojure-brasil (1)
- # clojure-dev (2)
- # clojure-russia (19)
- # clojure-spec (21)
- # clojure-uk (69)
- # clojurescript (23)
- # code-reviews (15)
- # cursive (3)
- # datavis (1)
- # datomic (8)
- # euroclojure (3)
- # events (5)
- # flambo (15)
- # hoplon (17)
- # jobs-rus (13)
- # lambdaisland (50)
- # mount (5)
- # off-topic (3)
- # om (1)
- # parinfer (72)
- # proton (1)
- # protorepl (1)
- # re-frame (17)
- # reagent (59)
- # videos (1)
I just posted a question to the Clojure ML - has anyone had any issues with danielz/system or stuartsierra/component when used with the latest alpha11?
I’m using lein (not boot) if that makes a difference… I started with a fresh closp template generated code which ran fine. Then I ran lein ancient upgrade on the project (using :allow-all) and now I’m getting errors related to (require vs (:require … afaik…
I replied on list - there are bugs in system, I have filed PRs, and they have been merged. There are also upstream problems in monger, which system pulls in.
@eraserhd: w.r.t. instrumentation, no -- the advice is to use generative testing to test the impl of functions
@eraserhd probably not hard to write a helper aimed at your use case, and you could throw it into https://github.com/gfredericks/schpec if you want
I have a weird tree data structure made out of vectors and numbers that has positional information in it. I did this mostly because I've written too much C. In Clojure, it's neither actually efficient, nor semantic. (You have to compute offsets for information.)
I was happy to discover I can actually specify the whole thing with spec. Though the conformed values aren't useful.
@gfredericks: Is there anything I can do to help https://github.com/gfredericks/schpec/pull/10 land? My first thought was “contribute review time”, but the two other open PRs seem to be blocked on upstream responding to feedback.
@lvh I have some minor concerns but I think they're all improvements that can be made later without breaking anything. Go ahead and merge it, I'll release later today
Sorry I had mistakenly thought everything was blocked on others
no worries, I’ve maintained open sores projects, I get stuff falling through the cracks 🙂
@lvh schpec 0.1.0 exists now
@gfredericks: awesome, thanks; I'll ship more features your way