Clj-kondo could in theory warn about (try (map ...))
because it can know about a set of functions that are lazy like map
via some data file like eastwood's var-info.edn. Maybe eastwood already has this feature?
As in, "top level expression inside try is lazy", so any exceptions thrown by evaluating the function on sequence elements are likely to be evaluated after the try exits, and won't be caught by your handlers? I don't recall if such a check is implemented in Eastwood off hand...
Reading through this section, it seems perhaps no: https://github.com/jonase/eastwood#unused-ret-vals
@andy.fingerhut Yes, someone was suggesting this for with-redefs
in #clj-kondo