Simplest fix I could think of was to build a nippy specific version (no cljs support) of encore that did not require core.async as part of its loading process.
I also upgraded the various memoize functions to use per-bucket locking features of concurrent hashmaps which removes the need for delay and deref.
A better pathway may be to using an getClassByName check or something like that that doesn't initiate the core.async loading process unnecessarily. Or potentially making the check for core.async a delayed check as opposed to a compile time check.
Simplest fix I could think of was to build a nippy specific version (no cljs support) of encore that did not require core.async as part of its loading process.
I also upgraded the various memoize functions to use per-bucket locking features of concurrent hashmaps which removes the need for delay and deref.
A better pathway may be to using an getClassByName check or something like that that doesn't initiate the core.async loading process unnecessarily. Or potentially making the check for core.async a delayed check as opposed to a compile time check.
Or nothing :-). Maybe not worth it :-).