Heh, based on that my guess is that no one has used lein-typed in CI builds. :) I've submitted a PR to Ambrose to exit with a non-zero code when type checking fails:
https://github.com/frenchy64/lein-typed/pull/1

Since lein-typed is brand new I imagine people have been writing there own tasks to do something similar for CI. Any CircleCI guys are on the list want to give us a real experience report?

On 9/30/13 5:26 PM, Stuart Halloway wrote:
Any experience reports?  My experience so far:

Type Checker: Found 1 error
$ echo $?
0




On Mon, Sep 30, 2013 at 7:20 PM, Ben Mabey <b...@benmabey.com <mailto:b...@benmabey.com>> wrote:

    On 9/30/13 5:16 PM, Stuart Halloway wrote:

        I tried the following experiment with type checking clojure.set:

        (ns exploring.core-typed
          (:use clojure.core.typed clojure.repl)
          (:require [clojure.set :as set]))

        (ann ^:no-check clojure.set/difference [(Set Any) (Set Any) ->
        (Set Any)])

        (set/difference #{1 2} [1 2])

        (comment
          (check-ns)
          )

        Is there an extant example that shows how this kind of safety
        check might be used in e.g. a CI build?

        Stu

    Seems like an invocation of `lein typed check`[1] would do the
    trick in a CI build...

    -Ben

    1. https://github.com/frenchy64/lein-typed

-- -- 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
    <mailto: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
    <mailto:clojure%2bunsubscr...@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
    <mailto:clojure%2bunsubscr...@googlegroups.com>.
    For more options, visit https://groups.google.com/groups/opt_out.


--
--
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/groups/opt_out.

--
--
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/groups/opt_out.

Reply via email to