Hm…bummer, @wilkerlucio when running in Debug mode the compiler generates a too large method for async-reader2, making it impossible to start a REPL.

core async dumps a lot of code, and it is hitting the JVM limit on method size

yeah, and its not helping that I have a lot of macros that makes those even bigger

needs to be split up, which would make it clearer probably as well 🙂

but the solution is not so simple, because of how go blocks work, if I break the function I have to add more message passing, which is more overhead

yep

them’s the cost of core async 🙂

yeah, I'm already unsatisfied with the amount of overhead from it as current, I'm trying to reduce it so I would like to avoid adding more now, do you know if its possible to increase the max method code size?

nope, that is a hard limit in JVM

65536 bytes, if I remember right

16-bit size field in the JVM internals I think

definitely causing me dev issues…being able to set jvm breakpoints is important for certain bugs, and I can’t do it anymore because of pathom

ok, I can take a look on it, can you please open an issue?

sure

@tony.kay 2.2.7 should work 😉

@souenzzo your updates to the diplomat are also in this release, thanks!