This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-22
Channels
- # announcements (1)
- # beginners (179)
- # boot (8)
- # calva (3)
- # cider (4)
- # clara (3)
- # cljdoc (31)
- # clojure (9)
- # clojure-austin (1)
- # clojure-chicago (5)
- # clojure-dev (19)
- # clojure-nl (2)
- # clojure-uk (1)
- # clojurescript (13)
- # core-matrix (1)
- # cursive (86)
- # datascript (2)
- # datomic (13)
- # emacs (3)
- # figwheel-main (1)
- # fulcro (66)
- # off-topic (250)
- # pathom (7)
- # re-frame (19)
- # reitit (5)
- # sql (37)
- # uncomplicate (5)
I have a question, iterator-seq
returns a lazy seq or not? I need to work with a possible infinite iterable class in Java.
Since iterators are lazy I think the answer has to be yes.
Or a better way to say it is that if the iterator is lazy, the sequence will be lazy.
Hi, folks. Can I give a name to a test case with clojure.test/are
?
Or how can I know which case failed in the report?
Some comments on this would be much appreciated: https://stackoverflow.com/questions/55797382/idiomatic-rest-wrappers-in-clojure
You may study a generic Swagger client, Martian (https://skillsmatter.com/meetups/8426-clojure-bytes); and also consider the Cognitect AWS client wrapper as a more sprawling example. By the way, maybe "Java 11" will eventually solve this, but here is a severe case of complecting. The two API wrappers you mentioned, and Martian, are coupled to Apache's HTTP Client; while Cognitect's AWS API wrapper apparently delegates to some Jetty thing. For "something special", I would like to mix and match: use any API wrapper with any HTTP library. If I have a biggish app that already has a way of managing HTTP connections, retries, pooling, throttling, etc.... with Netty, say... the API wrappers should participate in that!