Nice! I hadn't seen that before.
Thank you both.
On Sat, Mar 29, 2014 at 3:29 PM, Jonas wrote:
> You could give core.rrb-vector[1]. From the docs:
>
> The main API entry points are clojure.core.rrb-vector/catvec,
> performing vector concatenation, and clojure.core.rrb-vector/subvec, which
You could give core.rrb-vector[1]. From the docs:
The main API entry points are clojure.core.rrb-vector/catvec,
performing vector concatenation, and clojure.core.rrb-vector/subvec, which
produces a new vector containing the appropriate subrange of the input
vector (in contrast to clojure.co
If you do a (count @mem) it reports the length of the atom's vector isn't
growing without bounds. It seems counterintuitive that the parts of the
old vector wouldn't get garbage collected because the atom no longer points
to them. But I guess I need to rtfd.
Thank you.
On Sat, Mar 29, 2014 at
On Sat, Mar 29, 2014 at 10:09 AM, Ryan Waters wrote:
> I have some code that blows up the heap and I'm not sure why. I've
> reduced it down to the following.
>
> I've tried to make sure the atom doesn't have boundless growth and I
> didn't think 'while' hangs on to the head of sequences so I'm e
I have some code that blows up the heap and I'm not sure why. I've reduced
it down to the following.
I've tried to make sure the atom doesn't have boundless growth and I didn't
think 'while' hangs on to the head of sequences so I'm embarrassed to say
I'm stumped.
(defn leaks-memory
[]
(let
