One problem with Lisp is everything, including variable bindings, increases the nesting level making the code illegible. Last thing you want is for the type declaration to have their own nesting.
It's like Unix pipes for functions:
(~> "hello"
(string-ref 1)
(char->integer))[1] https://github.com/ruricolist/serapeum/blob/master/control-f...
[2] https://github.com/ruricolist/serapeum/blob/master/REFERENCE...
First you will usually want to write small chunks of code, instead of a large soup.
Second, you can make intentional decisions with your use of newlines in order to highlight specific aspects of the code.
I find clojure more readable than most other languages… However, bad code stands out horribly (which is actually great if you have at least one experienced engineer in the team- I’d argue there’s nothing worse than bad code that looks normal). Just like anything else, writing good lisp takes some skill.
Your specific editor and its configuration will also have a big impact on your experience.
(defun foo (&aux bar baz)
(setq bar (quux)
baz (xyzzy))
...)