but this got me thinking about a language that didn't have closures but could still model functional-style data transformation pipelines by inlining the map/filter/etc chain together with the function pointers' contents...

nevermind i just remembered function pointers exist.

chat i guess writing about your problems helps...

the idea is from codeforces.com/blog/entry/1...

TL;DR: if you focus your attention on pairs of points from the upper-left and lower-right "edges" of the point cloud, respectively, there's a nice property that lets you divide-and-conquer. do this a bunch of times and you get the answer for all pairs

these moon runes solve advent of code day 4. MOON RUNES

the neovim setup lacks the operator color coding of the online formatter (and it keeps complaining about the local formatter editing in the unicode symbols), might make a nicer integration plugin if i feel like it idk

im still not sold on enforced tacitness (planet notation is just another form of variable names to me) (do i just not get array programming?) but the inversion primitives are quite interesting

so is the notion of designing for as fluid of a feedback loop as possible