Eastwood is a Clojure lint tool. It analyzes Clojure source code in
projects, reporting things that may be errors.
Installation instructions are in the documentation here:
https://github.com/jonase/eastwood/#installation--quick-usage
Updates since the last release are described in the change log here:
https://github.com/jonase/eastwood/blob/master/changes.md#changes-from-version-014-to-015
The changes most visible to Eastwood users are:
-
New linter :local-shadows-var that warns if a local name (e.g. a
function argument or let binding) has the same name as a global Var, and is
called as a function. This is sometimes a mistake. More details with
examples here:
https://github.com/jonase/eastwood#local-shadows-var---a-local-name-that-is-same-as-a-global-name-called-as-a-function
-
New linter :wrong-tag that warns for some kinds of erroneous type tags.
For example, a primitive type tag like ^int or ^bytes on a Var name
being def'd or defn'd should be given as ^{:tag 'int} instead. Also it
is best if Java class names outside of the java.lang package are fully
qualified when used to hint the return type of a function on its argument
vector. More details with examples here:
https://github.com/jonase/eastwood#wrong-tag---an-incorrect-type-tag
-
New API for running Eastwood from a REPL session, nearly identical to
what is available from the command line. Note that this means you need not
use Leiningen at all to use Eastwood, even if the instructions are
currently Leiningen-specific. Instructions here:
https://github.com/jonase/eastwood#running-eastwood-in-a-repl
-
:unlimited-use warnings are no longer issued for the namespace
clojure.test. It is very common for Clojure developers to have (:use
clojure.test) in test namespaces. Issue #95
<https://github.com/jonase/eastwood/issues/95>.
- :suspicious-expression warnings are no longer issued for forms inside
quote forms. Issue #74 <https://github.com/jonase/eastwood/issues/74>.
For those who have asked, sorry, there is still no way to annotate
expressions in your source code to disable linters for expressions that you
know are ok, while leaving the linter enabled in the rest of the code.
That is coming.
Go squash some bugs!
Jonas Enlund, Nicola Mometto, and Andy Fingerhut
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
