set the channel topic: https://github.com/clavascript/cherry 🍒
Just pushed a new version of cherry-cljs to npm. Ported almost all fixes, etc from clavascript. I must say that it's becoming slightly annoying to have to maintain two almost identical code bases so I can't help that splitting some things into a library will make things easier, although there are sometimes tiny differences between the two. @mrdalloca if you want to help out (as you proposed in #squint), here are two issues that is just grunt work: https://github.com/clavascript/cherry/issues/57 https://github.com/clavascript/cherry/issues/58
should I submit as PR?
Yes
@borkdude it took me a while but now I'm starting on issue 57 😅
preview at https://github.com/tiagodalloca/cherry/tree/issue-57
Awesome!
perhaps custom reader macros would allow accounting for those differences
you’d need your own build process for that but given that these tools are themselves build tools may not be too out of reach
@mrdalloca has joined the channel