libera/commonlisp - IRC Chatlog
Search
13:27:37
Demosthenex
i'd love to have seen minecraft in lisp :P i know there was an abandoned POC version somewhere
15:14:20
beach
kagev: It used to be organized by ALU, the Association of Lisp Users. But I think that organization is dormant.
15:14:53
beach
I attended it in San Francisco and in Montreal. Perhaps in some other place as well, I can't remember.
15:48:26
NotThatRPG
ILC was very fun: I went to it in Cambridge, MA and Reno, NV. There was one more after that, but none sinse
17:06:41
NotThatRPG
Posted a PR and an issue. Wondering if you could have a peek; I have a proposed fix, but I'm not sure it's legit
17:13:45
NotThatRPG
One question, though: I have been running a relatively modest number of tests on each of the generators (which involves copying the generators for repeatability). I'm seeing SBCL give heap exhausted errors when I do this. Is there any reason this should be memory leaking?
17:21:37
NotThatRPG
Trying to test random-state, I go from Dynamic space usage is: 91,911,680 bytes. to Dynamic space usage is: 522,143,632 bytes. and error out.
17:39:56
NotThatRPG
It looks like the resources are being sucked up by KISS11. When I drop that from my test suite, the test-suite runs to completion (but repeatability tests all fail).
17:46:41
Bike
i just did a quick test locally, and it looks like some of the generators do copy enough - the dumb lcg and middle-square. mersenne 64 and 32 do seem to have a problem, though. are you seeing it fail on all generators?
17:49:47
Bike
it looks like the copy method on mersenne only does a shallow copy of the generator structure rather than actually copying the underlying arrays
17:50:55
NotThatRPG
Using CL:*RANDOM-STATE* caused errors for me in RANDOM-STATE on SBCL. I had to replace it with a new global as default value for RANDOM's GENERATOR argument
19:49:49
NotThatRPG
On SBCL, is it possible to extract the file causing the warning from a compiler warning? I'd really love to be able to quash style-warnings from a known-bad upstream library.
19:52:43
NotThatRPG
I have a case where I'm getting a compiler warning about a file with a compiler macro -- a call to the function was compiled before the call to the compiler macro. AFAICT there is no algorithm for me to find the call that should be moved or marked as notinline. So I would like to just shush this *specific* warning
20:06:57
edwlan[m]
One other option is to bind muffle-warnings to a handler that matches a satisfied type
20:07:58
edwlan[m]
You could probably also use a satisfies-type that checks the compile file pathname special variable