Try to give Eclipse more memory like this:
eclipse.exe -vm e:\jdk8\bin\javaw.exe -vmargs -Xms2048m -Xmx4096m
2014-11-01 13:12 GMT+08:00 Fluid Dynamics :
> On Saturday, November 1, 2014 12:09:33 AM UTC-4, Dylan Butman wrote:
>>
>> Is it hard to actually send the log? Are you purposefully uncooper
Hi Isaac,
On 01 Nov 2014, at 05:19, Isaac Karth wrote:
> Laurens, Using a PRF actually sounds very close to ideal for what I was
> looking for. If I can convert a map (or record) to a reproducible seed, and
> have that be independant from other random checks, that's pretty close to
> exactly
The way you wrote your loop it will only ever run once which means you
could take it out.
1> res = take from queue
2> if res nil? terminate
3> if res recur with result from with-open (always nil)
4> back to 2 and terminate
Not sure if this is intended but the way it is written it does not make
On Friday, October 31, 2014 11:19:19 PM UTC-5, Isaac Karth wrote:
>
> Looks like if I want to use libraries like clojure.data.generators or
> bigml.sampling I'd need to amend the random generators to replace calls to
> the Mersenne Twister function or (def ^:dynamic *rnd* (java.util.Random.
>
This thread needs to end, it's no longer productive.
Fluid Dynamics - file a ticket for CCW with information useful for
addressing the problem if you have it. Otherwise, I do not think there is
anything left that anyone can help you with here.
Everyone else - thank your for all the helpful co
Thanks for the responses! This is very helpful.
--
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 - please be patient with your
first post.
To
It would be great if someone could enumerate more explicitly what "better" test
output means. What are the specific problems in the current test output
reporting?
Similar problem list for test runner might be useful.
Discussion here is fine but ultimately needs to land on a design wiki page.
I
I can say for certain that at a minimum better indentation of data structures
to the console would be a must, a vector with 4+ hash maps in it are currently
unreadable and I have to copy to an editor to indent and analyze.
Beyond that, I can imagine the need for a structural diff that tells me
On Nov 1, 2014, at 1:58 PM, Alex Miller wrote:
> It would be great if someone could enumerate more explicitly what "better"
> test output means. What are the specific problems in the current test output
> reporting?
If there's any sort of consensus about test reporting, specifically how
diff
Additionally, I think it would be helpful to enumerate example (failing)
tests and their output by current clojure.test.
On Saturday, November 1, 2014 1:58:32 PM UTC-5, Alex Miller wrote:
>
> It would be great if someone could enumerate more explicitly what "better"
> test output means. What ar
http://jakemccrary.com/blog/2014/06/22/comparing-clojure-testing-libraries-output/
has some good examples. I'm currently using humane-test-output. It's worked
nicely for me.
'(Devin Walters)
> On Nov 1, 2014, at 7:00 PM, Alex Miller wrote:
>
> Additionally, I think it would be helpful to enum
11 matches
Mail list logo
