@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.
blah. sorry for misunderstanding. will rejigger tests
no worries. just out of curiority, are the PRs handwritten or also with the help of an LLM? (not bad or good, just wondering)
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
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
I'll just prompt you through the PR then ;)
sorry for the mess. i appreciate the patience
did you see my remark about the changelogs?
eep. sorry. will do
Hey thanks. Currently traveling back from the Conj so I’ll have a look at this later some time this week hopefully!
No hurry at ALL! Hope it was fun!
It sure was!
(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)