This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-14
Channels
- # announcements (10)
- # babashka (14)
- # beginners (51)
- # calva (2)
- # cider (28)
- # cljs-dev (1)
- # cljsrn (3)
- # clojure (185)
- # clojure-dev (15)
- # clojure-europe (6)
- # clojure-italy (2)
- # clojure-nl (6)
- # clojure-uk (45)
- # clojurescript (4)
- # conjure (12)
- # datomic (37)
- # duct (37)
- # figwheel-main (15)
- # helix (23)
- # interceptors (1)
- # jobs (1)
- # jobs-discuss (11)
- # jvm (5)
- # luminus (3)
- # malli (15)
- # off-topic (69)
- # pathom (8)
- # pedestal (2)
- # re-frame (7)
- # reagent (58)
- # reitit (33)
- # remote-jobs (1)
- # rum (14)
- # sci (7)
- # shadow-cljs (15)
- # spacemacs (9)
- # testing (19)
- # timbre (3)
- # tools-deps (14)
@alexmiller https://download.clojure.org seems to have an expired certificate
working on it as we speak
just waiting for cloudfront to distribute it
Has anybody here run into the need for labelled loop
-`recur`, where you could recur out into an enclosing loop? This would be a fantastic fit for tight interpreter-loops and - at least on js - already supported by labelled blocks / breaks ...
@bendlas there actually is a ticket and a patch for this that we are going to at least look at again for 1.11
looking for the link...
or https://ask.clojure.org/index.php/2790/add-named-loop-recur-to-facility-for-nested-loops
there have been a few times when I've wanted the named recur, but not many (and usually I take it as a sign that my code needs to be broken up more, but sometimes that's hard when doing perf stuff and closing over a lot of primitives etc)
Nice. I saw someone posting here on Slack a week or two ago with some code where they want to recur
out one level and it was hard to structure their code cleanly with just the current model of loop
/`recur`.