14:07:13pveHi, intrigued by White_Flame's "dot" macro suggestion, I tried implementing a version of it. I think it turned out alright, although I'm still unsure if it could be used to create truly readable code. Maybe in certain situations..
14:07:42pveWhite_Flame: thanks for the inspiration :)
14:10:55beachUsing operations is a much better idea that names of slots. But of course, I need to be careful with what I say, or else it will be branded as "oop nonsense".
14:11:30pveThere's one thing I'm wondering: should the default placement of the "current input value" to the chain of operations be first, or last. I.e. (+ _ 1 2 3) or (+ 1 2 3 _)
14:11:56pveit's hard for me to say which is better
14:13:56pvemany functions have keyword or rest parameters, which could mean that "first" is a better default
14:14:00hayleyI think "arrow" libraries have multiple macros, one macro for either case, and one which allows using a (rather unhygenic) name like <> to specify where the value should go.
14:17:58hayleyAs an aside I'm not a big fan of access-esque accessors, since you can write accidentally quadratic code when provided with lists rather than vectors, or perhaps alists rather than hash tables here.
14:21:41hayleyAnyways; underscore-predicate might be better written with AND rather than WHEN, and I like to use a pattern matching library for parsing list structure.