Is seqex still relevant?

[viebel]

@jclaggett @Chouser
I really enjoyed your talk at ClojureConj 2013!

But I have a question: now that we have clojure.spec, do we still need seqex?

The only thing I don't see in clojure.spec is syndoc. But maybe there is more.

cc: @trptcolin @rahulkavale

[jclaggett]

Hello Yehonathan,

I would say that clojure.spec is a good replacement for seqex. One simple
reason is that clojure.spec is part of Clojure directly and not a library.
Another reason is that I've not been able to actively work on seqex in some
time.

Regards and good luck coding,
Jonathan

On Thu, Oct 27, 2016 at 12:52 AM, Yehonathan Sharvit <
[email protected]> wrote:

I really enjoyed your talk at ClojureConj 2013!

But I have a question: now that we have clojure.spec, do we still need
seqex?

The only thing I don't see in clojure.spec is syndoc. But maybe there is
more.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#9, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGKLZf7BguVo616Lzf4P_8vcJxACaCWks5q4C4QgaJpZM4Kh8RD
.

[viebel]

Makes sense. Thx

On Thu, Nov 17, 2016, 23:44 Jonathan Claggett [email protected]
wrote:

Hello Yehonathan,

I would say that clojure.spec is a good replacement for seqex. One simple
reason is that clojure.spec is part of Clojure directly and not a library.
Another reason is that I've not been able to actively work on seqex in some
time.

Regards and good luck coding,
Jonathan

On Thu, Oct 27, 2016 at 12:52 AM, Yehonathan Sharvit <
[email protected]> wrote:

I really enjoyed your talk at ClojureConj 2013!

But I have a question: now that we have clojure.spec, do we still need
seqex?

The only thing I don't see in clojure.spec is syndoc. But maybe there is
more.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#9, or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAGKLZf7BguVo616Lzf4P_8vcJxACaCWks5q4C4QgaJpZM4Kh8RD

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#9 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA6VPlpoLxbjy0wVUhAdqZ56q6qHjfIcks5q_MqggaJpZM4Kh8RD
.