This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-06-28
Channels
- # announcements (1)
- # beginners (128)
- # calva (15)
- # cider (1)
- # clerk (4)
- # clj-kondo (10)
- # clojure-berlin (5)
- # clojure-denmark (2)
- # clojure-europe (59)
- # clojure-nl (2)
- # clojure-norway (83)
- # clojure-sweden (3)
- # clojure-uk (4)
- # cursive (11)
- # datomic (8)
- # emacs (13)
- # events (1)
- # hyperfiddle (3)
- # juxt (2)
- # malli (13)
- # nrepl (10)
- # off-topic (46)
- # releases (2)
- # reveal (1)
- # rewrite-clj (6)
- # sci (6)
- # scittle (17)
- # shadow-cljs (2)
- # xtdb (2)
- # yamlscript (8)
https://gist.github.com/ingydotnet/c7576a447ad9334a4503e0738ecb5f99
Anyone have an idea of what is going on with this?
"Method code too large" because I required clojure.core.async
?
https://stackoverflow.com/questions/35733558/large-defrecord-causes-method-code-too-large
is about the only related thing I find.
I'm just trying to add clojure.core.async
to YS
I’m not familiar with this issue unfortunately
Can't see enough there to be sure, but Method Too Large can result from any overlarge data literal (because Java doesn't have data-structure literals; it compiles to code that builds up the data structure). So the problem also occurs sometimes with core.match
or even, IIRC, case
. You work around it one way or another.
One workaround (if it really is obviously a data literal) is to read it from a resource with clojure.edn. No limit there, except of course the height and width of your computer.
I posted more in #sci I think I'm just giving too many arguments to a macro or something but I'm about to get an airplane so I can't investigate further. But yeah it looks like I can get around as pretty easily once I'm at my destination. Thanks for looking
Nothing to do with .async specifically
Just the straw that broke the macro's back 😊