This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-29
Channels
- # beginners (42)
- # boot (12)
- # cider (3)
- # cljs-dev (277)
- # cljsrn (44)
- # clojure (127)
- # clojure-austin (9)
- # clojure-austria (1)
- # clojure-brasil (14)
- # clojure-canada (1)
- # clojure-dev (22)
- # clojure-dusseldorf (1)
- # clojure-italy (4)
- # clojure-russia (24)
- # clojure-spec (33)
- # clojure-taiwan (1)
- # clojure-uk (21)
- # clojure-ukraine (8)
- # clojurescript (134)
- # core-async (41)
- # core-logic (8)
- # cursive (1)
- # datomic (3)
- # ethereum (1)
- # events (4)
- # funcool (1)
- # leiningen (12)
- # off-topic (21)
- # om (19)
- # onyx (45)
- # overtone (1)
- # parinfer (2)
- # pedestal (3)
- # proton (2)
- # re-frame (103)
- # reagent (48)
- # test-check (27)
- # untangled (51)
- # vim (3)
is it expected? (i am fairly sure it used to work, the <type>Range optimisations probably broke this)
I guess it should work as the docstring for range says "Returns a lazy seq of ..." even tho it's not really a lazyseq anymore
range automatically realizes the first chunk so it's answering truthfully
Oh sorry, I'm not awake yet :)
You're right in that it's not lazy
yeah, both docstrings mention lazy-seqs, sounds/looks like a bug caused by optimisations
Or at least not like it was
It's not a bug as much as realized? Not being as useful as it could be imo
It would be better if realized? returned true if not lazy
There is a ticket for this I think
that too, but something lazy as a (range ...) should work like it used to imho, the end user don't care that it's was optimised at some point
I don't find that using realized? on lazy seqs is particularly helpful ever
me neither, I just used it to test something (see in #clojure the issue with c.c.jdbc)
something else I am trying to update a large'ish project to 1.9 from 1.8 and I get this weird error when I try to launch a repl:
Exception in thread "main" java.lang.NoClassDefFoundError: clojure/core$second__4347, compiling:(controller.clj:1:1)
I have no clue why so far. really odd (I tried alpha 1, 12, 13, same result)
ok, for posterity: that was caused by "direct-linked" dependency, if anyone ever encounters the same pb. Now I ll shut up
FWIW I have a similar issue that occasionally is thrown from a shutdown hook when my project is aot-compiled using direct linking: java.lang.NoClassDefFoundError: com/stuartsierra/component$update_system_reverse$fn__1373
I have had no luck reproducing a simple test case, alas