Hello
I'm not working actively on clojure-hadoop, so maybe eslick's and clizzin's
forks could be more advanced (although I hadn't looked onto changes).
I think, that fragmentation of libraries is not so good thing, so I invite
everybody who wants to participate in development to join mailing list
A while back the discussion on the "bounded memoize" thread in this
forum lead to Meikel writing up a nice summary of how to do caching,
providing a pluggable strategy: lru, ttl, fifo, etc. Meikel's writeup
can be found at
http://kotka.de/blog/2010/03/memoize_done_right.html
It presents a bunch of
And if you don't have time to read the whole blog post - it's very
detailed - and just read code, you could scroll down to cgrand's
memoize8 function at https://gist.github.com/330644
On Feb 6, 8:32 pm, Eugen Dück wrote:
> A while back the discussion on the "bounded memoize" thread in this
> foru
On Feb 6, 12:32 pm, Eugen Dück wrote:
> A while back the discussion on the "bounded memoize" thread in this
> forum lead to Meikel writing up a nice summary of how to do caching,
> providing a pluggable strategy: lru, ttl, fifo, etc. Meikel's writeup
> can be found athttp://kotka.de/blog/2010/03/m
Hi Eugen,
2011/2/6 Eugen Dück :
> scan -> email would be more convenient for me.
>
> @Chistopher
>> people keep citing it as some unique requirement foisted upon the community
>> by a power hungry dictator
>
> That's a generalization that lacks any relation to this thread, and I
> guess even the
> Back to the git pull request question - nobody seems to know anything
> about it, but that issue should not be related to legal issues, if
> clojure maintainers pull only stuff from CA signers, right?
Be careful about applying the word "should" to legal issues. I'm
inclined to just trust Rich an
The problem is that defrecord explicitly defines the interface you are
trying to implement, so you are effectively attempting to declare the
interface twice. And since clojure.lang.seqable isnt a protocol, you
cant redefine it with extend. So, you will have to rewrite the
defrecord macro or similar
I also found it useful to define my own clojure.core. This is because
i wanted swap! and reset! to work on my AtomHash. So i did something
like this, using clj-nstools.
http://code.google.com/p/clj-nstools/
ns+ is sort of slow for large projects, but im sure that can be
improved.
(ns clj.core
(:
do you really need that? How about an infinite lazy sequence?
(defn infinite [arg]
(lazy-seq
(Thread/sleep 2000) ;;simulate 2 second retrieval time
(concat (for [i (range 0 arg)]
i) (infinite arg
(def a (infinite 3))
(first a) ;;=> sleep 2 seconds, return 0
(take 3 (filter
> Not every potential contributor lives in downtown
> Megalopolis, Coastal State, USA.
Agreed, but you must see that your particular case lays at the
extreme.
I'm of the opinion that if someone is inclined to contribute, then
they will not be deterred by the cost of a postage stamp -- par avion
o
Forgive me if I'm misunderstanding, but you don't need to import a
protocol to use it. If you need to actually get ahold of the protocol
(say, to implement another deftype/defrecord), you can just use
`require` or `use` to get ahold of it:
(ns stuff
(:use [com.example-ns :only [IFoo])
On Sun, Feb 6, 2011 at 3:55 PM, Fogus wrote:
>> Not every potential contributor lives in downtown
>> Megalopolis, Coastal State, USA.
>
> Agreed, but you must see that your particular case lays at the
> extreme.
Does it really? 20% of the population of the US still lives outside of
major cities.
> A while back the discussion on the "bounded memoize"
A truly classic thread, immortalized in JoC and at
https://github.com/fogus/anamnesis
:-)
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegrou
> Does it really? 20% of the population of the US
> still lives outside of major cities. That's
> not a majority but it's hardly an "extreme"
> minority either.
I'm sorry, I was referring more to your description of a treacherous
hike through a vast winter wonderland; not of the hordes of potentia
> Same here. In my case, snail-mail would mean a 2.5km hike through a
> freezing winter wonderland to the nearest mailbox that's used to send
> rather than being receive-only. So, 5 km there and back. It could
> easily take over two hours and might even be dangerous depending on
> the weather.
Thi
On Sun, Feb 6, 2011 at 4:44 PM, Eric Lavigne wrote:
>> Same here. In my case, snail-mail would mean a 2.5km hike through a
>> freezing winter wonderland to the nearest mailbox that's used to send
>> rather than being receive-only. So, 5 km there and back. It could
>> easily take over two hours and
On Sat, 5 Feb 2011 20:42:54 -0500
Christopher Petrilli wrote:
> On Sat, Feb 5, 2011 at 1:23 PM, Mike Meyer
> wrote:
> > On Sat, 5 Feb 2011 00:09:41 -0500
> > Christopher Petrilli wrote:
> >> For example, the following projects REQUIRE contributor agreements, in
> >> writing, signed and either sc
Hi Olek,
I haven't found time to work more on it lately, but checked the
current status of the codebase today.
It appears that all new work is going into Textmash2, a rewrite in
Clojure, if I understand it correctly ?
I have some questions:
* Is your intent to replace eventually the java version
On Feb 6, 2:08 pm, Seth wrote:
> (filter #(= % 2) a)
Another way:
(filter #{2} a)
--
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 - plea
On Feb 3, 12:22 am, Andy Fingerhut wrote:
> I've done a pass through most of the Clojure programs on the shootout
> web site recently, making some of them faster, and choosing -Xmx
> command line arguments when running them to keep the memory usage down
> to a reasonable level -- not always
>> For $1, they will convert an email or PDF into an old fashioned letter
>> and put it in the mail for you.
>>
> If a snail-mail generated that way would be acceptable for submitting
> a CA, I can't fathom why a fax or an e-mail direct to Hickey (bearing
> a scanned signed written document) wouldn
> * Is your intent to replace eventually the java version with the
> clojure version ? If so, how do you deal with the concern of "quick
> startup time" ?
An idea: jEdit optionally lets you start a background server during
system startup so that firing up jEdit can be fast later. Maybe
something s
22 matches
Mail list logo
