Re: [ANN] Clojure 1.10.0-beta8

Absolutely not trying to propel this discussion forward, but *ackchyually *even with the given semantics ("async-require should be used in asynchronous code"), the better word would be "concurrent" or "multithreaded". But I certainly didn't intend this thread to unwind so much and take away

Re: [ANN] Clojure 1.10.0-beta8

For sure, but some documentation of that process would be nice, otherwise the “nah, were good” replies come off as condescending. I’ve typed up a few other comments, and then deleted them, as they’re getting too OT. So I’ll exit the conversation, and unsub from this mailing list, since it’s clear

Re: [ANN] Clojure 1.10.0-beta8

Geez, man, relax and have a drumstick. The audience for this is, I expect, small. Over time we expect to monkey with the internals of require itself, and this will basically become deprecated, but that was too much for this point in 1.10. Also, please note that the other two parts of this beta

Re: [ANN] Clojure 1.10.0-beta8

I suspect Alex and other folks have already done all of the bikeshedding internally that they have the patience for, and are content with the name and the reasons they ahve for it, and are not enthusiastic about another round of that in a public forum. Rich owns Clojure code legally, and I would

Re: [ANN] Clojure 1.10.0-beta8

>> We’re good with the name. The docstring exists for further explanation. Except the code is less-readable. The name is meaningless. "async-require" appends the adverb "async" to the verb "require", therefore making it an asynchronous variant of require, which is exactly the opposite of what

Re: [ANN] Clojure 1.10.0-beta8

Agreed, specifically to avoid things like this: https://github.com/tech-ascent/tech.compute/blob/master/src/tech/compute/cpu/tensor_math.clj#L45 Great timing and we will be looking forward to it! On Wed, Nov 21, 2018 at 11:09 AM Sean Corfield wrote: > This makes me smile… My first reaction to

RE: [ANN] Clojure 1.10.0-beta8

This makes me smile… My first reaction to the name was the same as Alexander’s and then my second reaction cut in: “No, they’ll have thought about the name and won’t entertain changes”  It’s for safely doing requires in asynchronous (multi-threaded) code. Sean Corfield -- (970) FOR-SEAN --

Re: [ANN] Clojure 1.10.0-beta8

We’re good with the name. The docstring exists for further explanation. > On Nov 21, 2018, at 11:29 AM, Alexander Yakushev wrote: > > Could I suggest bikeshedding on the name async-require? Before I've seen the > patch, my initial impression was that it loads namespaces asynchronously > (that

Re: Confused by a bit of syntax-- Clojure(script) or Hiccup?

I've also discovered that ":<>" isn't even in the docs/ directory at all. Fortunately, the couple of places it is used in the examples document it as shorthand for React.Fragment. Randy On Tue, Nov 20, 2018 at 12:49 PM Justin Smith wrote: > I'll add that I knew this, but it took me longer than

Re: [ANN] Clojure 1.10.0-beta8

Could I suggest bikeshedding on the name async-require? Before I've seen the patch, my initial impression was that it loads namespaces asynchronously (that is, returns control immediately and loads them in the background). It might be somewhat confusing that a function async-require is

[ANN] Clojure 1.10.0-beta8

1.10.0-beta8 is now available. You can try it with clj using: clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.10.0-beta8"}}}' Changes in 1.10.0-beta8: - CLJ-2438 - demunge source location in execution error messages - CLJ-2437

[ANN] martian 0.1.9 - simplify your HTTP clients

Hi everyone, I am pleased to announce the release of martian 0.1.9 Martian provides an abstraction allowing you to describe the HTTP endpoints that you call without methods, urls and query parameters leaking into your application code, allowing you to work