This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-24
Channels
- # adventofcode (13)
- # beginners (163)
- # boot (8)
- # cider (1)
- # clojure (86)
- # clojure-germany (1)
- # clojure-italy (2)
- # clojure-spec (66)
- # clojure-switzerland (1)
- # clojure-uk (25)
- # clojured (1)
- # clojurescript (58)
- # core-async (1)
- # cursive (4)
- # datomic (11)
- # events (1)
- # funcool (3)
- # hoplon (86)
- # off-topic (8)
- # om (11)
- # onyx (1)
- # protorepl (7)
- # re-frame (15)
- # ring-swagger (4)
@bhauman I really like the use of iterate in your solutions. Most of my searches are still loop-recurs, that's a really cool way to structure search.
@angusiguess thanks! iterate allows you to operate on the list of individual states that result from each step, loop has less overhead but requires more thinking 🙂
Yeah, that's the bit. Any time I could prevent some heavily nested destructuring would be nice.
24 is pretty good. I really liked 23 too, a lil' bit of manual jitting
@angusiguess I looked at you stuff the other day, the other thing I would recommend is to take advantage of read-string 🙂
Hahaha, yeah there's a lot of regular expression use in there admittedly.
Luckily you've probably got loads of bfs code already written