This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-04
Channels
- # announcements (19)
- # babashka (11)
- # babashka-sci-dev (9)
- # beginners (71)
- # calva (25)
- # cider (1)
- # clara (36)
- # clj-kondo (47)
- # clojure (65)
- # clojure-dev (64)
- # clojure-europe (9)
- # clojure-nl (2)
- # clojure-seattle (1)
- # clojure-uk (2)
- # clojured (8)
- # clojurescript (17)
- # cursive (9)
- # data-science (36)
- # datahike (11)
- # emacs (10)
- # figwheel-main (19)
- # fulcro (15)
- # graalvm (12)
- # humbleui (5)
- # introduce-yourself (3)
- # jobs (10)
- # leiningen (4)
- # lsp (24)
- # malli (7)
- # nextjournal (23)
- # off-topic (1)
- # pedestal (2)
- # polylith (6)
- # portal (1)
- # re-frame (3)
- # reitit (2)
- # releases (2)
- # remote-jobs (1)
- # reveal (9)
- # shadow-cljs (13)
- # spacemacs (6)
- # xtdb (3)
Babashka 0.7.7 Changelogs: https://github.com/babashka/babashka/blob/master/CHANGELOG.md
🎉 5
@borkdude why java.lang.StackOverflowError [at <repl>:3:1] is rising?
@mike1452 This has to do with the printing of the value. I haven't dug into why it happens, but just not printing the result will take care of the problem.
thank you.
Yeah, I checked too. in JVM at-at has no error.
I found the issue. The print-method
implementations aren't triggered properly for records in SCI. If you remove them, then then on the JVM printing the record will cause a stackoverflow too.
👍 1
Oh, thank you. I’ll try.