This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-22
Channels
- # announcements (7)
- # babashka (17)
- # beginners (45)
- # biff (2)
- # cider (16)
- # clj-on-windows (3)
- # cljs-dev (12)
- # clojure (27)
- # clojure-austin (1)
- # clojure-europe (18)
- # clojure-norway (5)
- # clojurescript (36)
- # conjure (35)
- # core-async (2)
- # datascript (4)
- # datomic (4)
- # emacs (15)
- # fulcro (23)
- # holy-lambda (12)
- # hyperfiddle (1)
- # introduce-yourself (5)
- # nbb (11)
- # off-topic (37)
- # pathom (34)
- # pedestal (9)
- # reitit (4)
- # releases (1)
- # remote-jobs (1)
- # sci (5)
- # scittle (3)
- # shadow-cljs (88)
- # tools-build (4)
@borkdude i remember that was possible to control things like "max stack size", "max recur limit", "max list size" in sci. But I can't find docs about it.
@souenzzo There was something like this very early on but it was removed because of several reasons: performance, but also: once you want this level of control, you usually also want timeout control, etc and SCI can't offers this: the host runtime should be able to do this. I've got something like this working in the #nbb REPL: when you type (range)
there it's stuck, but you can press ctrl-c to interrupt the "vm" and then it's back into the REPL. Another very simple way to prevent such a problem is to use print-length.