This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-08
Channels
- # announcements (6)
- # atom-editor (1)
- # babashka (21)
- # beginners (70)
- # clerk (4)
- # clj-kondo (71)
- # clj-yaml (1)
- # clojure (54)
- # clojure-art (1)
- # clojure-denmark (1)
- # clojure-dev (1)
- # clojure-doc (1)
- # clojure-europe (31)
- # clojure-nl (1)
- # clojure-norway (41)
- # clojure-uk (15)
- # clojurescript (36)
- # conjure (1)
- # cursive (2)
- # datomic (14)
- # duct (10)
- # emacs (12)
- # etaoin (176)
- # gratitude (25)
- # hyperfiddle (17)
- # jobs (1)
- # juxt (5)
- # london-clojurians (1)
- # malli (3)
- # nbb (21)
- # off-topic (29)
- # reitit (12)
- # releases (2)
- # remote-jobs (7)
- # shadow-cljs (9)
- # testing (9)
Does anyone have any strategies they like to verify that a function returns an actually lazy sequence?
is realized?
not working for your use case?
https://clojuredocs.org/clojure.core/realized_q
https://clojuredocs.org/clojure.core/realized_q#example-6220edd3e4b0b1e3652d75b1
😠2
I guess you can check for all these cases (impl of IReduceInit & co), but that seems quite convoluted. Maybe there's some other way
I wonder if mocking would be appropriate here. This may be a terrible idea, but could you create a special class that implements ISeq
but throws an exception if realized?