This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-12
Channels
- # aleph (8)
- # announcements (9)
- # babashka (15)
- # beginners (91)
- # calva (54)
- # chlorine-clover (3)
- # cider (25)
- # clj-kondo (9)
- # cljfx (4)
- # cljsrn (12)
- # clojure (40)
- # clojure-australia (2)
- # clojure-europe (77)
- # clojure-nl (10)
- # clojure-spec (22)
- # clojure-uk (9)
- # clojurescript (39)
- # conjure (12)
- # cursive (8)
- # datascript (17)
- # datomic (22)
- # emacs (2)
- # expound (6)
- # fulcro (25)
- # kaocha (7)
- # malli (9)
- # meander (5)
- # off-topic (13)
- # pathom (8)
- # pedestal (5)
- # portal (1)
- # rdf (58)
- # re-frame (65)
- # reagent (15)
- # sci (3)
- # shadow-cljs (50)
- # test-check (6)
- # testing (3)
- # tools-deps (1)
- # vim (7)
- # xtdb (10)
I'm considering dropping the :termination-safe
and :realize-max
options since https://github.com/borkdude/sci/issues/348 highlights a few cases which I think aren't fundamentally solvable (without lots of hacks).
Any thoughts/feelings on this?
Partially also said in the issue, I believe a generic solution that will work in every context is not possible , so better not to pretend it is. It would be nice to have the :invoke-callback
hook and some control over lazy sequences (via :realize-max). This control over lazy sequences could however also be implemented via the bindings so this doesn’t have to ship with Sci directly actually. Especially since range
is not the only case where something is realized this might reflect the actual situation better.