IRC channel logs


back to list of logs

<ArneBab>dthompson: maybe a source for inspiration for a game engine build on chickadee: (that’s common lisp)
<dsmith>sneek: botsnack
<dsmith>sneek: seen ArneBab
<sneek>ArneBab was last seen in #guile 21 minutes and 58 seconds ago, saying: dthompson: maybe a source for inspiration for a game engine build on chickadee: (that’s common lisp).
<dsmith>!yada yada yada
<sneek>I've been running for one minute and 1 second
<sneek>This system has been up 23 hours, 23 minutes
<dsmith>sneek: botsnack
*sneek wags
<sneek>I've been running for 2 minutes and 50 seconds
<sneek>This system has been up 23 hours, 47 minutes
<dsmith>sneek: botsnack
<dsmith>sneek: botsnack
<dsmith>sneek: seen pkill9
<sneek>pkill9 was last seen in #guix 7 minutes and 37 seconds ago, saying: guix*.
<dsmith>Ok, I'm done fussing with the bot. All back to normal.
<lechner>Hi, can Guile load the Init File from an XDG-compliant path?
<lloda>wanting to configure a module with some parameters. I only need to do it at import time. I see a few fugly ways to do it but is there a good one?
<old>By configuring you mean what exactly?
<old>Changing procedures? Changing global values?
<unmatched-paren>old: i think they mean like a module that can be passed arguments
<unmatched-paren>like a procedure, but it's a module
<unmatched-paren>(which is called a functor in ocaml and apparently chicken...)
<old>hmmm okay I see
<old>This looks like template programming in C++
<dsmith-work>Morning Greetings, Guilers
<sneek>I've been running for 6 minutes and 38 seconds
<sneek>This system has been up 1 day, 14 hours, 18 minutes
<old>Anybody ever get `;;; (what! #<stack 7fc048272320>)` when using statprof?
<antipode>It sounds familiar to me but I don't recall from where.
<dsmith-work>Error messages should have fun unique words so they are easy to locate in the source.
<old>Yeah I found the source location. Apparently it's when statprof failed to create a stack frame or cutting it
<old>I'm probably doing something wrong with partial-continuation
<lechner>Hi, is this still the recommended way to ensure proper mtimes for go files with automake?
***maximed is now known as antipode
<old>lampilelo: Do you think having a single condition variable shared by all futures is better than a single cond var for each of them?
<old>I've check ice-9 futures and it's doing the former, while I'm doing the latter. What do you think?
<old>Also what do you think of pinning every thread to a its core with setaffinity?