Re: New guide: Reading Clojure Characters

On Jun 17, 2017 3:45 PM, "Alex Miller" wrote: I cleaned up this section a bit. I favored "unused" over any of the other choices as I think that's the most accurate. +1 -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send ema

Re: New guide: Reading Clojure Characters

On Jun 17, 2017 4:04 PM, "Andy Fingerhut" wrote: I would recommend _against_ using the same parameter name multiple times like this, for the confusion in people's minds that it can easily create. completely agree. the problem is that you _can_ do this. which means the language is not quite w

Re: New guide: Reading Clojure Characters

I would recommend _against_ using the same parameter name multiple times like this, for the confusion in people's minds that it can easily create. If you avoid this practice, then it is irrelevant why the last value is used versus an earlier one. The foo2 function works for the same reason that fo

Re: New guide: Reading Clojure Characters

On Jun 17, 2017 3:36 PM, "Andy Fingerhut" wrote: Consider this Clojure 1.8.0 REPL session: user=> (defn foo [a a] [a a]) #'user/foo ser=> (foo 1 2) [2 2] user=> (defn foo2 [_ _] [_ _]) #'user/foo2 user=> (foo2 1 2) [2 2] This is the sense in which _ is just another function parameter na

Re: New guide: Reading Clojure Characters

I cleaned up this section a bit. I favored "unused" over any of the other choices as I think that's the most accurate. On Sat, Jun 17, 2017 at 1:51 PM, Gregg Reynolds wrote: > > suggestion: for '_' , Anonymous might be better than Irrelevant. Also, > maybe explicitly note that multiple _ are al

Re: New guide: Reading Clojure Characters

They would be gensymed, but those are a lot harder to read. I added a note about that and cleaned up that section a little more. On Sat, Jun 17, 2017 at 1:34 PM, Gregg Reynolds wrote: > > one question: the explanation of `%` uses macroexpand but shows eg arg1, > arg2, etc. wouldn't those be gen

Re: New guide: Reading Clojure Characters

Consider this Clojure 1.8.0 REPL session: user=> (defn foo [a a] [a a]) #'user/foo ser=> (foo 1 2) [2 2] user=> (defn foo2 [_ _] [_ _]) #'user/foo2 user=> (foo2 1 2) [2 2] This is the sense in which _ is just another function parameter name, no more or less special to the compiler than th

Re: New guide: Reading Clojure Characters

On Jun 17, 2017 1:55 PM, "Timothy Baldridge" wrote: Anonymous implies there might be some sort of auto gen going on (as there is with anonymous functions), Irrelevant has my vote therefore. The other characteristics are a side-effect of it being a naming convention (with no official support by th

Re: New guide: Reading Clojure Characters

Happy to have feedback, but best as issues or prs at https://github.com/clojure/clojure-site -- 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

Re: New guide: Reading Clojure Characters

Anonymous implies there might be some sort of auto gen going on (as there is with anonymous functions), Irrelevant has my vote therefore. The other characteristics are a side-effect of it being a naming convention (with no official support by the compiler). Maybe that could be pointed out in greate

Re: New guide: Reading Clojure Characters

On Jun 17, 2017 1:27 PM, "Alex Miller" wrote: A new guide is available on the Clojure site: https://clojure.org/guides/weird_characters suggestion: for '_' , Anonymous might be better than Irrelevant. Also, maybe explicitly note that multiple _ are allowed. ie it has 2 characteristics: you c

Re: New guide: Reading Clojure Characters

On Jun 17, 2017 1:27 PM, "Alex Miller" wrote: A new guide is available on the Clojure site: https://clojure.org/guides/weird_characters + 111... one question: the explanation of `%` uses macroexpand but shows eg arg1, arg2, etc. wouldn't those be gen-symed? thanks, gregg -- You received t

New guide: Reading Clojure Characters

A new guide is available on the Clojure site: https://clojure.org/guides/weird_characters Many thanks to James Hughes (who wrote the original blog post and donated the starting point for the guide). Many thanks also to Erik Assum, who started the PR and added a lot of things to it. And to Paulu

Re: Why transducers are not (yet) fundamental?

> On 17 Jun 2017, at 17:43, Alex Miller wrote: > > FAQ entry: > > https://clojure.org/guides/faq#transducers_vs_seqs > > Both have their place, in my opinion. I often use transducers with `into` > where I would have used ->> in the past, but not always - it depends on > context. > > While t

Re: Why transducers are not (yet) fundamental?

FAQ entry: https://clojure.org/guides/faq#transducers_vs_seqs Both have their place, in my opinion. I often use transducers with `into` where I would have used ->> in the past, but not always - it depends on context. While transducers will generally perform better if you have many transformat

Why transducers are not (yet) fundamental?

I'm doing a little research for a talk and asking clojurists around. The thesis I'm supporting is that transducers should completely replace "normal" (non-reducing based) sequential processing. People have different reactions to this, usually going from "what's wrong with threading macros" to "

Re: Seeking a function to partially parallelize collection processing

core.async pub/sub ? On Friday, June 16, 2017 at 10:13:11 AM UTC-4, Tom Connors wrote: > > I'm looking for a function that would likely be named something like > "sequential-by" or "parallel-per" that takes some data-producing thing like > a la