serapeum

What GP (probably) meant is that in Lisp you're supposed to write macros, and when you do, this "is simply not worse" than the dotted message sends: (-> params (op1 mod2) (op2 mod2)) params .op1(mod2) .op2(mod2) There's a reason why just about every Lisp currently in use[1] has `->`/`->>`[2] macros: they're just so easy to write that not having them would be strange. Same with |> in OCaml - with currying, it's literally just `let (|>) x f = f x;;`. So, while it's true that Lisp (or OCaml) base language doesn't have the particular convenience, it's also true that in Lisp (and, in this case, in OCaml) you are meant to extend the language to allow such conveniences. [1] With a glorious exception of PicoLisp, because quote is all you'll ever need. [2] And more! With `doto` you have Smalltalk/Dart cascades, with `nest` (https://gi

Obviously, also available in CL, in Serapeum library[1]. Racket is credited in the docstring (since it's ~> instead of ->). Also, `nest` works very well for unnesting forms[2] [1] https://github.com/ruricolist/serapeum/blob/master/control-f... [2] https://github.com/ruricolist/serapeum/blob/master/REFERENCE...

>named let Serapeum has you covered: https://github.com/ruricolist/serapeum/blob/master/REFERENCE...

> both are dynamic languages with types added later in? Common Lisp has always had types and type declarations (e.g. `the` in the hyperspec[1]) as it's part of the specification. It was not added later as far as I know. However, `declaim` and `declare` were left very underspecified so they tend to be very implementation-specific, though there are libraries that make types more portable[2][3]. [1] http://www.lispworks.com/documentation/HyperSpec/Body/s_the.... [2] https://github.com/lisp-maintainers/defstar [3] https://github.com/ruricolist/serapeum/blob/master/REFERENCE...

I consider Serapeum to be a revamp of the Common Lisp standard: https://github.com/ruricolist/serapeum/blob/master/REFERENCE.... This provides a bunch of new features and idioms including ideas borrowed from newer languages like Clojure. Great example of "growing a language" as a long-term evolutionary process that doesn't require changing earlier specifications in incompatible ways.