> And here I thought I was telling you that not everybody uses "first-class" (or even "first-class values") in precisely the same way. I know of no other defin

> And here I thought I was telling you that not everybody uses "first-class" (or even "first-class values") in precisely the same way. I know of no other definition of 'first-class value', which is an established concept since at least Scheme was invented in the mid 70s, which made functions true first class values. The idea that procedures in some programming languages were not first-class seem to come from C. Stratchey from the mid 60s, where functions in Algol can't be the result of compound expressions, can't be stored in variables and data structures. > It would be perfectly clear to call it "first-class naming" If someone would define it and give it some useful semantics, it might be clear. > I didn't mean to imply that Clojure invented callable arrays, merely that Clojure programs use them frequently; probably just as frequently as they use higher-order functions. This podcast speaks exactly how an error introduced by callable data influenced the developer leave Clojure for Haskell: https://building.fireside.fm/37 https://building.fireside.fm/37