Re: :refer-clojure broken?

Never mind. For some reason I had (:require [clojure.core :refer :all] ...) after(:refer-clojure :exclude [print println print-str]) . Sorry about the bother. Gregg On Tue, Sep 15, 2015 at 1:22 PM, Gregg Reynolds wrote: > > > On Sun, Sep 13, 2015 at 9:23 PM, Alex Miller wrote: > >> C

Re: deftype code reload oddity

Here's another bit of strangeness. I tried putting my interfaces file at the root (see https://github.com/migae/datastore/tree/master/src/clojure); this seems to work ok. Then I fooled around with profiles etc. to try to avoid having Interfaces.clj ever be reloaded - it's only needed once, for ao

Re: lazy-seq and threads

Hi, Thanks for looking into my questions. I posted a self contained example here https://github.com/coreasync/parallel-gzip with instructions how to create test data as well. Also attached results below I get on my quite decent hardware (partial 'time' results are mangled, was not sure how to sepa

Re: Unexpected behavior for symbols or keywords used in the operator position

Aha, got it. Just surprised me that it still worked without a map. Thanks for clearing it up! Cheers On Tuesday, September 15, 2015 at 10:29:08 PM UTC-6, Carlo wrote: > > Symbols and keywords act as functions which look themselves up in their > argument. Essentially: > > ('sym map) => (get ma

Re: Unexpected behavior for symbols or keywords used in the operator position

Symbols and keywords act as functions which look themselves up in their argument. Essentially: ('sym map) => (get map 'sym) ('sym map not-found) => (get map 'sym not-found) (:key map) => (get map :key) (:key map not-found) => (get map :key not-found) It's often pretty useful, in my experie

Unexpected behavior for symbols or keywords used in the operator position

Hello All: Noticed the following works in Clojure 1.6 and 1.7 (didn't test prior to that): user=> ('+ 'a 'b) b Also "works" for any set of symbols: user=> ('abra 'ka 'dabra) dabra My expectation was that using symbols or keywords in the function/operator position would throw an exception sim

Re: Clojure/Pedestal vs Go

On Sep 15, 2015, at 20:45, Mikera wrote: > > 7. The open source library ecosystem on the JVM is awesome. There's nothing > like it for any other language. I like your other points, but in my experience this one is (arguably) no longer true. I've often found the JVM library ecosystem to be lack

Re: Clojure/Pedestal vs Go

Go is fine for system-level programming, but I personally wouldn't use it as a web application programming language. Ten reasons to consider.: 1. There isn't really much speed difference on micro-benchmarks between JVM code and Go. See e.g.: http://benchmarksgame.alioth.debian.org/u64q/go.html

Re: Clojure/Pedestal vs Go

I also am no Go expert. All I'll add is that I overheard that the lead author rejected a proposal to add `map` to the language, stating that it is "too niche". Doesn't bode well for FP in Go... -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post

Libraries for dealing with DNS

Does anyone have a recommendation or know of a good library to interact with DNS? I've found com.brweber2/clj-dns, but it is dated and I get NullPointerExceptions doing basic lookups. -- Kyle Sexton -- You received this message because you are subscribed to the Google Groups "Clojure" group.

Write Clojure & tackle tough problems for a promising start up

My advanced apologies if posting this job to the group is inappropriate. I preemptively searched this topic and most people seemed to say it's OK. Curbside is enabling a new way to shop, built for the era of instant mobile commerce. The Curbside App allows you to find, buy and seamlessly pick u

Re: Using metadata to specify how calls to a macro should be indented

This is an interesting proposal, and I like it in general. Everything in Cursive is based on extensions identified by the head form, like this: (style/register-formatting :clojure.core/def :only-indent) (style/register-formatting :clojure.core/defn- :only-indent) (style/register-formatting resolve

Oxford (UK) Clojure Group

Hi, I've seen a previous thread https://groups.google.com/forum/#!topic/clojure/dRPF8bEpjBE where a Clojure group in Oxford was mentioned. I don't know what happened to Oxjure but I'm interested in running a group and meeting people around Clojure and more extensively LISP. I've been to a Cloju

Re: Using metadata to specify how calls to a macro should be indented

On Sunday, September 13, 2015 at 8:25:42 AM UTC-4, Artur Malabarba wrote: > > > On 13 Sep 2015 12:33 pm, "Matching Socks" > wrote: > > > > Unless clojure.core itself will carry these annotations, could the > keyword be namespaced? > > Or do you mean it should be ::indent? (i.e., carry the names

Re: :refer-clojure broken?

On Sun, Sep 13, 2015 at 9:23 PM, Alex Miller wrote: > Can you be more specific about how you are loading the namespace? > Sorry for not getting back to you sooner, I did a little more experimenting to no avail. You can see it in action at migae datastore .

Re: Clojure/Pedestal vs Go

At least in one area -- data infrastructure -- the JVM has no competitors for off-the-shelf solutions. Hadoop, Spark, Storm, Kafka, Cassandra, HBase, etc etc are all JVM-based. In the alpha-nerd set, one can easily argue that the relevance of Go is fading and its being replaced by Rust. I'm not

Re: Clojure/Pedestal vs Go

Alan, Absolutely no need to apologize! :) I would hardly consider myself an expert either, I’m basing my understanding on the experiences I’ve had at my day job and the large body of developing articles and blogposts related to the language that seem to pop up at a near-constant rate on your fa

Re: Clojure/Pedestal vs Go

Max, You obviously know way more than I do about Go... I stand corrected, thanks. I did know that it doesn't support TCO so it doesn't surprise me that other language features went the wrong way too. I did not mean to misinform anyone, my apologies for speaking beyond my core competency (Go is

Re: lazy-seq and threads

I had the same question - are you running independent thread-isolated lazy-seqs on different sources in different threads? Or are you creating one lazy-seq and then *using* it to do different things in multiple threads? In the first case, the synchronization in lazy-seq only happens in a thread

Re: [ANN] Clojure 1.8.0-alpha5

Glad to hear it! On Tue, Sep 15, 2015 at 10:19 AM, Tom Marble wrote: > On Friday, September 11, 2015 at 8:41:34 AM UTC-5, Alex Miller wrote: >> >> Clojure 1.8.0-alpha5 is now available. >> > > I am pleased to report that this version of Clojure builds fine with the > early access version of JDK

Re: [ANN] Clojure 1.8.0-alpha5

On Friday, September 11, 2015 at 8:41:34 AM UTC-5, Alex Miller wrote: > > Clojure 1.8.0-alpha5 is now available. > I am pleased to report that this version of Clojure builds fine with the early access version of JDK 9 (w/jigsaw): http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-September/

Re: Martin Thompson: "Designing for Performance" video

The keynote is quite good, too: https://youtu.be/oxjT7veKi9c?list=PLEx5khR4g7PKFs3Y-gWd8TX4Y_5yTyUTP "Shared Mutable State: The most feared words in computing" - quite a bit of overlap with the ideals of Clojure. Alan On Tue, Sep 15, 2015 at 5:43 AM, Alan Thompson wrote: > If you haven't

Re: Clojure/Pedestal vs Go

Hi Alan, >From my experience this is not true: Go does not provide generics and actively >resists what most of us would consider good functional programming--Go is very >opinionated and doesn't allow much deviation from these opinions, by design. >So implementing practical immutable data struc

Re: lazy-seq and threads

Do you have a corresponding example of the parallel code? I'm not sure which part(s) are being delegated to other threads. Often it is just the I/O cost of reading the file that is the dominant cost, so parallelism doesn't buy you much. Alan On Mon, Sep 14, 2015 at 9:10 PM, Andy L wrote: > Hi

Martin Thompson: "Designing for Performance" video

If you haven't seen any of Martin's talks before, you should give this one a try. It is one of his best and reminds me a lot of Rich's best talks. This one is motivated by getting higher performance from code, but most of it emphasizes good design fundamentals as the basis for everything else. h