cherry

borkdude 2022-09-06T13:20:26.154579Z

set the channel topic: https://github.com/clavascript/cherry 🍒

borkdude 2022-09-06T16:20:27.997889Z

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

👍 1
😹 1
🥱 1
Tiago Dall'Oca 2022-09-06T18:03:20.468599Z

should I submit as PR?

borkdude 2022-09-06T20:20:29.524159Z

Yes

Tiago Dall'Oca 2022-10-03T20:07:43.883629Z

@borkdude it took me a while but now I'm starting on issue 57 😅

Tiago Dall'Oca 2022-10-03T20:07:47.344649Z

preview at https://github.com/tiagodalloca/cherry/tree/issue-57

borkdude 2022-10-03T20:13:22.373679Z

Awesome!

Aleed 2022-09-07T13:55:46.980199Z

perhaps custom reader macros would allow accounting for those differences

Aleed 2022-09-07T13:56:21.096949Z

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

Tiago Dall'Oca 2022-09-06T16:20:31.279069Z

@mrdalloca has joined the channel