This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-11
Channels
- # announcements (4)
- # babashka (4)
- # beginners (164)
- # calva (47)
- # cider (1)
- # cljs-dev (29)
- # cljsrn (3)
- # clojure (137)
- # clojure-europe (23)
- # clojure-nl (3)
- # clojure-spec (7)
- # clojure-uk (44)
- # clojurescript (35)
- # component (8)
- # conjure (119)
- # cursive (32)
- # datomic (12)
- # emacs (31)
- # figwheel-main (36)
- # graalvm (10)
- # jobs (2)
- # kaocha (1)
- # lein-figwheel (3)
- # meander (15)
- # mount (3)
- # off-topic (9)
- # pathom (8)
- # quil (4)
- # re-frame (13)
- # reagent (15)
- # remote-jobs (10)
- # shadow-cljs (128)
- # slack-help (2)
- # spacemacs (8)
- # test-check (6)
- # xtdb (6)
@bhauman hrm a bunch of users have already gone through that I'm pretty sure it's not redundant
@alexmiller website could use bump
@alexmiller there seems to be a problem in the latest core.async release.
------ WARNING #1 - :undeclared-var --------------------------------------------
Resource: cljs/core/async.cljs:396:15
--------------------------------------------------------------------------------
393 | but can be determined by the close? parameter.
394 |
395 | Returns a channel which will close after the items are copied."
396 | ([ch coll] (onto-chan ch coll true))
---------------------^----------------------------------------------------------
Use of undeclared Var cljs.core.async/onto-chan
--------------------------------------------------------------------------------
397 | ([ch coll close?]
398 | (go-loop [vs (seq coll)]
399 | (if (and vs (>! ch (first vs)))
400 | (recur (next vs))
--------------------------------------------------------------------------------
onto-chan should still exist, just deprecated
ah, that is a bug there though
alex: just curious, anyone reported compiler stack overflow after upgrading to 1.1.587 (from 1.0.567)?
I had this issue but didn’t have time to track it down or write a proper ticket, unfortunately travis logs are gone now, downgraded instead: https://github.com/binaryage/dirac/commit/2a47dcce1f9b93e16566f95cfa642ddef3b38511
it is probably on my side, will have to dive deeper, the stack trace looks like this: https://travis-ci.org/github/binaryage/dirac/builds/675503493#L571
seems like it would be good to capture that for David or someone to look at
@thheller core.async 1.2.603 is on its way, will probably be available in ~15 min
since it affects only my test code, I have a hunch that this hacky code could be causing it: https://github.com/binaryage/dirac/blob/master/src/automation/dirac/automation.clj#L27-L37 something in new core.async could affect it