This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-01
Channels
- # adventofcode (2)
- # announcements (3)
- # babashka-sci-dev (79)
- # beginners (76)
- # biff (2)
- # calva (32)
- # cider (2)
- # clj-kondo (42)
- # clj-on-windows (17)
- # clojure (28)
- # clojure-belgium (1)
- # clojure-berlin (1)
- # clojure-europe (95)
- # clojure-nl (4)
- # clojure-norway (4)
- # clojure-uk (5)
- # clojurescript (27)
- # conjure (5)
- # cursive (3)
- # data-science (16)
- # datomic (67)
- # graalvm (12)
- # hyperfiddle (36)
- # jobs (3)
- # jobs-discuss (1)
- # kaocha (2)
- # klipse (1)
- # leiningen (28)
- # lsp (16)
- # luminus (3)
- # malli (10)
- # nrepl (3)
- # off-topic (57)
- # other-languages (18)
- # re-frame (4)
- # reitit (8)
- # releases (1)
- # remote-jobs (1)
- # scittle (4)
- # shadow-cljs (7)
- # test-check (1)
- # tools-deps (4)
- # vim (11)
- # xtdb (25)
I'm really happy that the improved error message support (by means of exposing sci/stacktrace
and sci/format-stacktrace
) makes a huge difference with respect to error reporting in the Scittle powered ClojureScript playground at https://jurjanpaul.github.io/ape-cljs-playground/ !
Very much appreciating @borkdude's help with that!
@jurjanpaul502 Nice work. I've been considering making evaluation async, so you can write:
(require '[reagent.core])
and it would lazy load the reagent file from the CDN. And this would also allow you to do the load-from-url
thing, but baked in and it would not have the async problem you have now, since the next expression would be evaluated as a chained promiseIt would be a breaking change though, since people who rely on scittle.core.eval_string
being synchronous now, would then have a promise instead
Sounds like a very good idea to me! (I wouldn't mind adapting my code at all, but it would seemingly impact one or more other projects as well.)