Fork me on GitHub
#yamlscript
<
2024-06-28
>
Ingy döt Net20:06:29

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?

Ingy döt Net20:06:27

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

Daniel Craig21:06:31

I’m not familiar with this issue unfortunately

phill23:06:23

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.

phill23:06:59

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.

Ingy döt Net23:06:06

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

Ingy döt Net23:06:29

Nothing to do with .async specifically

Ingy döt Net23:06:58

Just the straw that broke the macro's back 😊