cherry

wcohen 2025-11-15T18:30:24.925249Z

@borkdude forgive the flurry of bug reports with potentially inartful associated PRs — I’m trying to get a cherry-native core async working (so that core.async.flow can work on JS) and it’s a bit of a stress test of protocols. The go blocks are of course more or less totally simplified away but there’s still nice coordination around channels I’m working through.

💪 1
wcohen 2025-11-17T16:47:53.100039Z

blah. sorry for misunderstanding. will rejigger tests

borkdude 2025-11-17T16:48:29.406909Z

no worries. just out of curiority, are the PRs handwritten or also with the help of an LLM? (not bad or good, just wondering)

wcohen 2025-11-17T16:49:21.249209Z

llm assistance. compilers are magic to me. i’m trying to de-llm the reports but i kind of liked the additional detail in the commit messages

wcohen 2025-11-17T16:50:01.155849Z

i’ve got an actual use case i’m trying to run against — the stacked up branches do seem to solve it, but i’m more than willing to accept that the llm messed up all the tests etc, and can try to take a closer look at justifications etc

borkdude 2025-11-17T16:50:14.067679Z

I'll just prompt you through the PR then ;)

wcohen 2025-11-17T16:50:32.036989Z

sorry for the mess. i appreciate the patience

borkdude 2025-11-17T18:14:24.843499Z

did you see my remark about the changelogs?

wcohen 2025-11-17T18:15:12.994419Z

eep. sorry. will do

borkdude 2025-11-15T18:49:40.306789Z

Hey thanks. Currently traveling back from the Conj so I’ll have a look at this later some time this week hopefully!

wcohen 2025-11-15T18:50:05.305429Z

No hurry at ALL! Hope it was fun!

❤️ 1
borkdude 2025-11-15T18:50:59.614409Z

It sure was!

wcohen 2025-11-15T18:32:30.171269Z

(I want that macro-based DSL from the prior discussion to be able to be transformed into a core async flow which is then executed in JS as a web analogue to what’s on JVM)