This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-10
Channels
- # announcements (5)
- # aws (18)
- # babashka (1)
- # beginners (81)
- # calva (7)
- # chlorine-clover (1)
- # cider (5)
- # cljs-dev (8)
- # clojure (125)
- # clojure-dev (1)
- # clojure-europe (31)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-norway (1)
- # clojure-spec (5)
- # clojure-sweden (1)
- # clojure-uk (31)
- # clojurescript (85)
- # code-reviews (1)
- # core-async (17)
- # cursive (39)
- # datomic (16)
- # emacs (1)
- # fulcro (6)
- # java (16)
- # kaocha (2)
- # luminus (4)
- # malli (2)
- # off-topic (65)
- # pathom (3)
- # re-frame (11)
- # reagent (5)
- # remote-jobs (1)
- # rum (5)
- # sci (10)
- # shadow-cljs (24)
- # spacemacs (4)
- # test-check (3)
- # tools-deps (22)
- # xtdb (15)
goood morniiiiiiiing
TIL https://excalidraw.com/ and I like it! “Sloppiness: cartoonist”
(repeat (* 365 75) 'good-morning)
?
Leap years. sigh
I just implicitly deducted those from expected lifespan Who's gonna know
75 is not thaaat optimistic.
Or do you plan to leave this channel when you’re going to retire?
isn't it? I thought that was WAY optimistic
I think pestilence-confiment may be messing with my outlook
(not to mention That Brexit)
No that seems about right, for people born in Belgium in 1983 (like me) the life expectancy is 73.8. I do plan to beat those odds. For kids born now it's 80+
@plexus everybody consideres himself above average 😛
Today I used babashka to create a Makefile based on output of a lein plugin. I need a shower now.
How do we feel about something like this?
(defn ->s+t
{:examples '[(->s+t "VSBPLATDTA" "PLPLAP") => :VSBPLATDTA.PLPLAP]}
[schema table]
(keyword (str (name schema) "." (name table))))
(defn split-segments
{:examples '[(split-segments :VSBPLATDTA.PLPLAP) => ["VSBPLATDTA" "PLPLAP"]]}
[kw-or-str]
(str/split (name kw-or-str) #"\."))
tempted to just implement this in Kaocha and call it a thing now. Maybe we can even get cljdoc to pick it up.
I've long considered implementing my own version of doctests (as in elixir, python, ...), but sticking code into strings in a homoiconic language seems wrong. The only benefit of the doctest approach is that it automatically shows up in docs.
Maybe :examples can be just a regular hashmap or a vector of tuples if order is important (which probably isn’t), which makes it trivial to parse and hook up to tests.
yeah that's just regular metadata. Not sure parsing would be an issue, this is trivial to parse too
interesting
What about examples that need apply with e.g. (range) or throw exceptions? My feeling is that you will be back to :test metadata for these cases and at least it’s supported by vanilla Clojure.test as well (forgive me my not using formatting and random capital letters, I’m on a mobile phone)
You can put whatever form you like in there. Test metadata is near to useless in my opinion because it doesn't fail in a way that is actionable, you just get an assertion error. Unless you drag in Clojure.test in all your namespace so you can define proper assertions.
Hey folks, @plexus's last sentence made me think. Would you care to comment on the following ClojureVerse topic? https://clojureverse.org/t/another-topic-on-inline-unit-tests-in-clojure/6209