curry/partial Lassi Kortela 01 Nov 2019 22:18 UTC
> I have a pre-pre-SRFI for a > currying lambda which the author called lambda*; I'd be happy to call it > lambda/curry. Lambda/opt would also work for me. SRFI 26, which defines the `cut` and `cute` macros, has an interesting and hilarious discussion of currying in Scheme. "The original name proposed for this SRFI was curry which immediately stirred some emotions as it does not what is commonly known as currying. Some alternatives have been discussed, such as section, specialise, specialize, partial-apply, partial-call, partial-lambda, _j, _i, $, &, srfi-26, foobar, xyz, schoenfinkelize, curry-which-isnt-curry, tandoori, and it has also been suggested to pick a five letter symbol uniformly at random and fix this as a name." We got off easy with SRFI 177. Nowadays Clojure has `partial`; Racket has `curry` in core but also `partial` in some frameworks or libraries. I guess many would assume `lambda/opt` means optional arguments.